curl/tests/data/test833

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

#
# Server-side
<reply>
<servercmd>
AUTH CRAM-MD5 PLAIN
REPLY "AUTHENTICATE CRAM-MD5" + Rubbish
REPLY * A002 NO AUTH exchange cancelled by client
REPLY "AUTHENTICATE PLAIN" +
REPLY AHVzZXIAc2VjcmV0 A003 OK AUTHENTICATE completed
</servercmd>
<data>
From: me@somewhere
To: fake@nowhere

body

--
  yours sincerely
</data>
</reply>

#
# Client-side
<client>
<server>
imap
</server>
<features>
crypto
</features>
 <name>
IMAP CRAM-MD5 authentication with SASL downgrade
 </name>
 <command>
'imap://%HOSTIP:%IMAPPORT/%TESTNUMBER/;MAILINDEX=1' -u user:secret
</command>
</client>

#
# Verify data after the test has been "shot"
<verify>
<protocol>
A001 CAPABILITY
A002 AUTHENTICATE CRAM-MD5
*
A003 AUTHENTICATE PLAIN
AHVzZXIAc2VjcmV0
A004 SELECT %TESTNUMBER
A005 FETCH 1 BODY[]
A006 LOGOUT
</protocol>
</verify>
</testcase>
tests: Added IMAP SASL downgrade tests 2013-12-22 17:10:50 -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`
			`SASL AUTH PLAIN`
tests: made the SASL modes separate keywords 2014-03-15 06:13:13 -04:00			`SASL DOWNGRADE`
tests: Added IMAP SASL downgrade tests 2013-12-22 17:10:50 -05:00			`RFC2195`
			`</keywords>`
			`</info>`

			`#`
			`# Server-side`
			`<reply>`
			`<servercmd>`
			`AUTH CRAM-MD5 PLAIN`
			`REPLY "AUTHENTICATE CRAM-MD5" + Rubbish`
			`REPLY * A002 NO AUTH exchange cancelled by client`
			`REPLY "AUTHENTICATE PLAIN" +`
sasl: Don't send authcid as authzid for the PLAIN mechanism as per RFC 4616 RFC 4616 specifies the authzid is optional in the client authentication message and that the server will derive the authorisation identity (authzid) from the authentication identity (authcid) when not specified by the client. 2019-04-18 16:54:35 -04:00			`REPLY AHVzZXIAc2VjcmV0 A003 OK AUTHENTICATE completed`
tests: Added IMAP SASL downgrade tests 2013-12-22 17:10:50 -05:00			`</servercmd>`
			`<data>`
			`From: me@somewhere`
			`To: fake@nowhere`

			`body`

			`--`
			`yours sincerely`
			`</data>`
			`</reply>`

			`#`
			`# Client-side`
			`<client>`
			`<server>`
			`imap`
			`</server>`
			`<features>`
			`crypto`
			`</features>`
			`<name>`
			`IMAP CRAM-MD5 authentication with SASL downgrade`
			`</name>`
			`<command>`
tests: use %TESTNUMBER instead of fixed number This makes the tests easier to copy and relocate to other test numbers without having to update content. Closes #6738 2021-03-12 11:38:26 -05:00			`'imap://%HOSTIP:%IMAPPORT/%TESTNUMBER/;MAILINDEX=1' -u user:secret`
tests: Added IMAP SASL downgrade tests 2013-12-22 17:10:50 -05:00			`</command>`
			`</client>`

			`#`
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<protocol>`
			`A001 CAPABILITY`
			`A002 AUTHENTICATE CRAM-MD5`
			`*`
			`A003 AUTHENTICATE PLAIN`
sasl: Don't send authcid as authzid for the PLAIN mechanism as per RFC 4616 RFC 4616 specifies the authzid is optional in the client authentication message and that the server will derive the authorisation identity (authzid) from the authentication identity (authcid) when not specified by the client. 2019-04-18 16:54:35 -04:00			`AHVzZXIAc2VjcmV0`
tests: use %TESTNUMBER instead of fixed number This makes the tests easier to copy and relocate to other test numbers without having to update content. Closes #6738 2021-03-12 11:38:26 -05:00			`A004 SELECT %TESTNUMBER`
tests: Added IMAP SASL downgrade tests 2013-12-22 17:10:50 -05:00			`A005 FETCH 1 BODY[]`
			`A006 LOGOUT`
			`</protocol>`
			`</verify>`
			`</testcase>`