<testcase> <info> <keywords> POP3 SASL SASL AUTH OAUTH2 RFC1734 RFC5034 RFC6749 RFC7628 </keywords> </info> # # Server-side <reply> <servercmd> AUTH OAUTHBEARER REPLY AUTH + REPLY %b64[n,a=user,%01host=127.0.0.1%01port=%POP3PORT%01auth=Bearer mF_9.B5f-4.1JqM%01%01]b64% + eyJzdGF0dXMiOiJpbnZhbGlkX3Rva2VuIiwic2NvcGUiOiJleGFtcGxlX3Njb3BlIiwib3BlbmlkLWNvbmZpZ3VyYXRpb24iOiJodHRwczovL2V4YW1wbGUuY29tLy53ZWxsLWtub3duL29wZW5pZC1jb25maWd1cmF0aW9uIn0 REPLY AQ== -ERR Authentication failed </servercmd> </reply> # # Client-side <client> <server> pop3 </server> <name> POP3 OAuth 2.0 (OAUTHBEARER) failure as continuation </name> <command> pop3://%HOSTIP:%POP3PORT/%TESTNUMBER -u user --oauth2-bearer mF_9.B5f-4.1JqM </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> CAPA AUTH OAUTHBEARER %b64[n,a=user,%01host=127.0.0.1%01port=%POP3PORT%01auth=Bearer mF_9.B5f-4.1JqM%01%01]b64% AQ== </protocol> </verify> </testcase>