curl/tests/data/test948

<testcase>
<info>
<keywords>
SMTP
SASL
SASL AUTH OAUTH2
RFC4954
RFC6749
RFC7628
</keywords>
</info>

#
# Server-side
<reply>
<servercmd>
AUTH OAUTHBEARER
REPLY AUTH 334 OAUTHBEARER supported
REPLY %b64[n,a=user,%01host=127.0.0.1%01port=%SMTPPORT%01auth=Bearer mF_9.B5f-4.1JqM%01%01]b64% 334 eyJzdGF0dXMiOiJpbnZhbGlkX3Rva2VuIiwic2NvcGUiOiJleGFtcGxlX3Njb3BlIiwib3BlbmlkLWNvbmZpZ3VyYXRpb24iOiJodHRwczovL2V4YW1wbGUuY29tLy53ZWxsLWtub3duL29wZW5pZC1jb25maWd1cmF0aW9uIn0
REPLY AQ== 535 Username and Password not accepted. Learn more at\r\n535 http://support.example.com/mail/oauth
</servercmd>
</reply>

#vi
# Client-side
<client>
<server>
smtp
</server>
 <name>
SMTP OAuth 2.0 (OAUTHBEARER) failure as continuation
 </name>
<stdin>
mail body
</stdin>
 <command>
smtp://%HOSTIP:%SMTPPORT/%TESTNUMBER --mail-rcpt recipient@example.com --mail-from sender@example.com -u user --oauth2-bearer mF_9.B5f-4.1JqM -T -
</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 "QUIT"
<protocol>
EHLO %TESTNUMBER
AUTH OAUTHBEARER
%b64[n,a=user,%01host=127.0.0.1%01port=%SMTPPORT%01auth=Bearer mF_9.B5f-4.1JqM%01%01]b64%
AQ==
</protocol>
</verify>
</testcase>
tests: Added OAUTHBEARER failure response tests 2015-11-16 01:36:59 +08:00			`<testcase>`
			`<info>`
			`<keywords>`
			`SMTP`
			`SASL`
			`SASL AUTH OAUTH2`
			`RFC4954`
			`RFC6749`
			`RFC7628`
			`</keywords>`
			`</info>`

			`#`
			`# Server-side`
			`<reply>`
			`<servercmd>`
			`AUTH OAUTHBEARER`
			`REPLY AUTH 334 OAUTHBEARER supported`
runtests: support dynamicly base64 encoded sections in tests This allows us to make test cases to use base64 at run-time and still use and verify information determined at run-time, such as the IMAP test server's port number in test 842. This change makes 12 tests run again that basically never ran since we moved to dynamic port numbers. ftpserver.pl is adjusted to load test instructions and test number from the preprocessed test file. FILEFORMAT.md now documents the new base64 encoding syntax. Reported-by: Marcel Raad Fixes #5761 Closes #5775 2020-08-04 19:56:12 +08:00			`REPLY %b64[n,a=user,%01host=127.0.0.1%01port=%SMTPPORT%01auth=Bearer mF_9.B5f-4.1JqM%01%01]b64% 334 eyJzdGF0dXMiOiJpbnZhbGlkX3Rva2VuIiwic2NvcGUiOiJleGFtcGxlX3Njb3BlIiwib3BlbmlkLWNvbmZpZ3VyYXRpb24iOiJodHRwczovL2V4YW1wbGUuY29tLy53ZWxsLWtub3duL29wZW5pZC1jb25maWd1cmF0aW9uIn0`
tests: Added OAUTHBEARER failure response tests 2015-11-16 01:36:59 +08:00			`REPLY AQ== 535 Username and Password not accepted. Learn more at\r\n535 http://support.example.com/mail/oauth`
			`</servercmd>`
			`</reply>`

			`#vi`
			`# Client-side`
			`<client>`
			`<server>`
			`smtp`
			`</server>`
			`<name>`
			`SMTP OAuth 2.0 (OAUTHBEARER) failure as continuation`
			`</name>`
			`<stdin>`
			`mail body`
			`</stdin>`
			`<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-13 00:38:26 +08:00			`smtp://%HOSTIP:%SMTPPORT/%TESTNUMBER --mail-rcpt recipient@example.com --mail-from sender@example.com -u user --oauth2-bearer mF_9.B5f-4.1JqM -T -`
tests: Added OAUTHBEARER failure response tests 2015-11-16 01:36:59 +08:00			`</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 "QUIT"`
			`<protocol>`
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-13 00:38:26 +08:00			`EHLO %TESTNUMBER`
tests: Added OAUTHBEARER failure response tests 2015-11-16 01:36:59 +08:00			`AUTH OAUTHBEARER`
runtests: support dynamicly base64 encoded sections in tests This allows us to make test cases to use base64 at run-time and still use and verify information determined at run-time, such as the IMAP test server's port number in test 842. This change makes 12 tests run again that basically never ran since we moved to dynamic port numbers. ftpserver.pl is adjusted to load test instructions and test number from the preprocessed test file. FILEFORMAT.md now documents the new base64 encoding syntax. Reported-by: Marcel Raad Fixes #5761 Closes #5775 2020-08-04 19:56:12 +08:00			`%b64[n,a=user,%01host=127.0.0.1%01port=%SMTPPORT%01auth=Bearer mF_9.B5f-4.1JqM%01%01]b64%`
tests: Added OAUTHBEARER failure response tests 2015-11-16 01:36:59 +08:00			`AQ==`
			`</protocol>`
			`</verify>`
			`</testcase>`