curl/tests/data/test865

<testcase>
<info>
<keywords>
POP3
SASL
SASL AUTH PLAIN
RFC1734
RFC4616
RFC5034
</keywords>
</info>

#
# Server-side
<reply>
<servercmd>
AUTH PLAIN
REPLY AUTH +
REPLY AHVzZXIAc2VjcmV0 +OK Login successful
</servercmd>
<data>
From: me@somewhere
To: fake@nowhere

body

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

#
# Client-side
<client>
<server>
pop3
</server>
 <name>
POP3 plain authentication
 </name>
 <command>
pop3://%HOSTIP:%POP3PORT/%TESTNUMBER -u user:secret
</command>
</client>

#
# Verify data after the test has been "shot"
<verify>
<protocol>
CAPA
AUTH PLAIN
AHVzZXIAc2VjcmV0
RETR %TESTNUMBER
QUIT
</protocol>
</verify>
</testcase>
tests: Added POP3 plain authentication test 2013-10-19 19:31:55 +08:00			`<testcase>`
			`<info>`
			`<keywords>`
			`POP3`
tests: Added "SASL" authentication keyword 2014-03-30 18:20:19 +08: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 19:01:15 +08:00			`SASL AUTH PLAIN`
tests: Added POP3 plain authentication test 2013-10-19 19:31:55 +08:00			`RFC1734`
			`RFC4616`
			`RFC5034`
			`</keywords>`
			`</info>`

			`#`
			`# Server-side`
			`<reply>`
			`<servercmd>`
			`AUTH PLAIN`
			`REPLY AUTH +`
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-19 04:54:35 +08:00			`REPLY AHVzZXIAc2VjcmV0 +OK Login successful`
tests: Added POP3 plain authentication test 2013-10-19 19:31:55 +08:00			`</servercmd>`
			`<data>`
			`From: me@somewhere`
			`To: fake@nowhere`

			`body`

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

			`#`
			`# Client-side`
			`<client>`
			`<server>`
			`pop3`
			`</server>`
			`<name>`
			`POP3 plain authentication`
			`</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-13 00:38:26 +08:00			`pop3://%HOSTIP:%POP3PORT/%TESTNUMBER -u user:secret`
tests: Added POP3 plain authentication test 2013-10-19 19:31:55 +08:00			`</command>`
			`</client>`

			`#`
			`# Verify data after the test has been "shot"`
			`<verify>`
			`<protocol>`
			`CAPA`
			`AUTH 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-19 04:54:35 +08: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-13 00:38:26 +08:00			`RETR %TESTNUMBER`
tests: Added POP3 plain authentication test 2013-10-19 19:31:55 +08:00			`QUIT`
			`</protocol>`
			`</verify>`
			`</testcase>`