curl/tests/data/test834

<testcase>
<info>
<keywords>
IMAP
SASL
SASL AUTH NTLM
SASL AUTH PLAIN
SASL DOWNGRADE
</keywords>
</info>

#
# Server-side
<reply>
<servercmd>
AUTH NTLM PLAIN
REPLY "AUTHENTICATE NTLM" +
REPLY TlRMTVNTUAABAAAABoIIAAAAAAAAAAAAAAAAAAAAAAA= + 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>
NTLM
SSL
!SSPI
</features>
 <name>
IMAP NTLM authentication with SASL downgrade
 </name>
 <setenv>
# we force our own host name, in order to make the test machine independent
CURL_GETHOSTNAME=curlhost
# we try to use the LD_PRELOAD hack, if not a debug build
LD_PRELOAD=%PWD/libtest/.libs/libhostname.so
 </setenv>
 <command>
'imap://%HOSTIP:%IMAPPORT/%TESTNUMBER/;MAILINDEX=1' -u user:secret
</command>
<precheck>
chkhostname curlhost
</precheck>
</client>

#
# Verify data after the test has been "shot"
<verify>
<protocol>
A001 CAPABILITY
A002 AUTHENTICATE NTLM
TlRMTVNTUAABAAAABoIIAAAAAAAAAAAAAAAAAAAAAAA=
*
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 NTLM`
			`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			`</keywords>`
			`</info>`

			`#`
			`# Server-side`
			`<reply>`
			`<servercmd>`
			`AUTH NTLM PLAIN`
			`REPLY "AUTHENTICATE NTLM" +`
			`REPLY TlRMTVNTUAABAAAABoIIAAAAAAAAAAAAAAAAAAAAAAA= + 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>`
			`NTLM`
tests: Change NTLM tests to require SSL Prior to this change tests that required NTLM feature did not require SSL feature. There are pending changes to cmake builds that will allow enabling NTLM in non-SSL builds in Windows. In that case the NTLM auth strings created are different from what is expected by the NTLM tests and they fail: "The issue with NTLM is that previous non-SSL builds would not enable NTLM and so the NTLM tests would be skipped." Assisted-by: marc-groundctl@users.noreply.github.com Ref: https://github.com/curl/curl/pull/4717#issuecomment-566218729 Closes https://github.com/curl/curl/pull/4768 2019-12-29 15:23:25 -05:00			`SSL`
tests: Disabled NTLM tests when running with SSPI enabled 2013-12-28 15:22:22 -05:00			`!SSPI`
tests: Added IMAP SASL downgrade tests 2013-12-22 17:10:50 -05:00			`</features>`
			`<name>`
			`IMAP NTLM authentication with SASL downgrade`
			`</name>`
			`<setenv>`
			`# we force our own host name, in order to make the test machine independent`
			`CURL_GETHOSTNAME=curlhost`
			`# we try to use the LD_PRELOAD hack, if not a debug build`
			`LD_PRELOAD=%PWD/libtest/.libs/libhostname.so`
			`</setenv>`
			`<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>`
			`<precheck>`
			`chkhostname curlhost`
			`</precheck>`
			`</client>`

			`#`
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<protocol>`
			`A001 CAPABILITY`
			`A002 AUTHENTICATE NTLM`
			`TlRMTVNTUAABAAAABoIIAAAAAAAAAAAAAAAAAAAAAAA=`
			`*`
			`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>`