curl/tests/data/test830

<testcase>
<info>
<keywords>
IMAP
SASL
SASL AUTH CRAM-MD5
SASL CANCELLATION
RFC2195
</keywords>
</info>

#
# Server-side
<reply>
<servercmd>
AUTH CRAM-MD5
CAPA LOGINDISABLED
REPLY AUTHENTICATE + Rubbish
REPLY * A002 NO AUTH exchange cancelled by client
</servercmd>
</reply>

#
# Client-side
<client>
<server>
imap
</server>
<features>
crypto
</features>
 <name>
IMAP CRAM-MD5 graceful cancellation
 </name>
 <command>
'imap://%HOSTIP:%IMAPPORT/830/;MAILINDEX=1' -u user:secret
</command>
</client>

#
# Verify data after the test has been "shot"
<verify>
# 67 - CURLE_LOGIN_DENIED
<errorcode>
67
</errorcode>
#
# The multi interface considers a broken "CONNECT" as a prematurely broken
# transfer and such a connection will not get a "LOGOUT"
<protocol>
A001 CAPABILITY
A002 AUTHENTICATE CRAM-MD5
*
</protocol>
</verify>
</testcase>
tests: Added IMAP graceful authentication cancellation tests 2013-11-23 09:26:33 -05:00			`<testcase>`
			`<info>`
			`<keywords>`
			`IMAP`
tests: Added "SASL" authentication keyword 2014-03-30 06:20:19 -04:00			`SASL`
tests: Replaced email authentication keywords with SASL based keywords As the email protocols implement SASL authentication rather than IMAP, POP3 and SMTP specific authentication, updated the authentication keywords to reflect this. 2014-03-30 07:01:15 -04:00			`SASL AUTH CRAM-MD5`
tests: made the SASL modes separate keywords 2014-03-15 06:13:13 -04:00			`SASL CANCELLATION`
tests: Added IMAP graceful authentication cancellation tests 2013-11-23 09:26:33 -05:00			`RFC2195`
			`</keywords>`
			`</info>`

			`#`
			`# Server-side`
			`<reply>`
			`<servercmd>`
			`AUTH CRAM-MD5`
imap/pop3/smtp: Added support for SASL authentication downgrades Added support for downgrading the SASL authentication mechanism when the decoding of CRAM-MD5, DIGEST-MD5 and NTLM messages fails. This enhances the previously added support for graceful cancellation by allowing the client to retry a lesser SASL mechanism such as LOGIN or PLAIN, or even APOP / clear text (in the case of POP3 and IMAP) when supported by the server. 2013-12-18 15:44:20 -05:00			`CAPA LOGINDISABLED`
tests: Added IMAP graceful authentication cancellation tests 2013-11-23 09:26:33 -05:00			`REPLY AUTHENTICATE + Rubbish`
			`REPLY * A002 NO AUTH exchange cancelled by client`
			`</servercmd>`
			`</reply>`

			`#`
			`# Client-side`
			`<client>`
			`<server>`
			`imap`
			`</server>`
			`<features>`
			`crypto`
			`</features>`
			`<name>`
			`IMAP CRAM-MD5 graceful cancellation`
			`</name>`
			`<command>`
imap: change from "FETCH" to "UID FETCH" ... and add "MAILINDEX". As described in #2789, this is a suggested solution. Changing UID=xx to actually get mail with UID xx and add "MAILINDEX" to get a mail with a special index in the mail box (old behavior). So MAILINDEX=1 gives the first non deleted mail in the mail box. Fixes #2789 Closes #2815 2018-07-31 07:12:18 -04:00			`'imap://%HOSTIP:%IMAPPORT/830/;MAILINDEX=1' -u user:secret`
tests: Added IMAP graceful authentication cancellation tests 2013-11-23 09:26:33 -05:00			`</command>`
			`</client>`

			`#`
			`# Verify data after the test has been "shot"`
			`<verify>`
			`# 67 - CURLE_LOGIN_DENIED`
			`<errorcode>`
			`67`
			`</errorcode>`
tests: Removed expected QUIT response from graceful cancellation tests A failure during authentication, which is performed as part of the CONNECT phrase (for IMAP, POP3 and SMTP) is considered by the multi- interface as being closed prematurely (aka a dead connection). As such these protocols cannot issue the relevant QUIT or LOGOUT command. Temporarily fixed the test cases until we can fix this properly. 2013-11-24 05:59:59 -05:00			`#`
			`# The multi interface considers a broken "CONNECT" as a prematurely broken`
			`# transfer and such a connection will not get a "LOGOUT"`
tests: Added IMAP graceful authentication cancellation tests 2013-11-23 09:26:33 -05:00			`<protocol>`
			`A001 CAPABILITY`
			`A002 AUTHENTICATE CRAM-MD5`
			`*`
			`</protocol>`
			`</verify>`
			`</testcase>`