1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
|
<?xml version="1.0" encoding="US-ASCII"?>
<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% + %b64[{"status":"invalid_token","scope":"example_scope","openid-configuration":"https://example.com/.well-known/openid-configuration"}]b64%
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 crlf="yes">
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>
|
