-
Notifications
You must be signed in to change notification settings - Fork 39
Expand file tree
/
Copy pathspec-references.ts
More file actions
131 lines (122 loc) · 7.42 KB
/
spec-references.ts
File metadata and controls
131 lines (122 loc) · 7.42 KB
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
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
/**
* Specification references for server OAuth conformance tests.
*
* Links test checks to relevant specifications:
* - RFC 9728 (Protected Resource Metadata)
* - RFC 8414 (Authorization Server Metadata)
* - RFC 7591 (Dynamic Client Registration)
* - RFC 6750 (Bearer Token Usage)
* - OAuth 2.1 Draft (Client Credentials, Token Endpoint Auth)
* - MCP Authorization Specification (2025-06-18)
*/
import { SpecReference } from '../../types';
export const ServerAuthSpecReferences: { [key: string]: SpecReference } = {
// ─────────────────────────────────────────────────────────────────────────
// RFC 9728: Protected Resource Metadata
// ─────────────────────────────────────────────────────────────────────────
RFC_9728_PRM_DISCOVERY: {
id: 'RFC-9728-discovery',
url: 'https://www.rfc-editor.org/rfc/rfc9728.html#section-3'
},
RFC_9728_PRM_RESPONSE: {
id: 'RFC-9728-response',
url: 'https://www.rfc-editor.org/rfc/rfc9728.html#section-3.2'
},
RFC_9728_WWW_AUTHENTICATE: {
id: 'RFC-9728-www-authenticate',
url: 'https://www.rfc-editor.org/rfc/rfc9728.html#section-5'
},
// ─────────────────────────────────────────────────────────────────────────
// RFC 8414: Authorization Server Metadata
// ─────────────────────────────────────────────────────────────────────────
RFC_8414_AS_DISCOVERY: {
id: 'RFC-8414-discovery',
url: 'https://www.rfc-editor.org/rfc/rfc8414.html#section-3'
},
RFC_8414_AS_FIELDS: {
id: 'RFC-8414-fields',
url: 'https://www.rfc-editor.org/rfc/rfc8414.html#section-2'
},
// ─────────────────────────────────────────────────────────────────────────
// RFC 7591: Dynamic Client Registration (DCR)
// ─────────────────────────────────────────────────────────────────────────
RFC_7591_DCR_ENDPOINT: {
id: 'RFC-7591-endpoint',
url: 'https://www.rfc-editor.org/rfc/rfc7591.html#section-3'
},
RFC_7591_DCR_REQUEST: {
id: 'RFC-7591-request',
url: 'https://www.rfc-editor.org/rfc/rfc7591.html#section-3.1'
},
RFC_7591_DCR_RESPONSE: {
id: 'RFC-7591-response',
url: 'https://www.rfc-editor.org/rfc/rfc7591.html#section-3.2'
},
// ─────────────────────────────────────────────────────────────────────────
// RFC 6750: Bearer Token Usage
// ─────────────────────────────────────────────────────────────────────────
RFC_6750_BEARER_TOKEN: {
id: 'RFC-6750-bearer',
url: 'https://www.rfc-editor.org/rfc/rfc6750.html#section-2.1'
},
RFC_6750_WWW_AUTHENTICATE: {
id: 'RFC-6750-www-authenticate',
url: 'https://www.rfc-editor.org/rfc/rfc6750.html#section-3'
},
RFC_6750_INSUFFICIENT_SCOPE: {
id: 'RFC-6750-insufficient-scope',
url: 'https://www.rfc-editor.org/rfc/rfc6750.html#section-3.1'
},
// ─────────────────────────────────────────────────────────────────────────
// RFC 7235: HTTP Authentication
// ─────────────────────────────────────────────────────────────────────────
RFC_7235_401_RESPONSE: {
id: 'RFC-7235-401',
url: 'https://www.rfc-editor.org/rfc/rfc7235.html#section-3.1'
},
RFC_7235_WWW_AUTHENTICATE: {
id: 'RFC-7235-www-authenticate',
url: 'https://www.rfc-editor.org/rfc/rfc7235.html#section-4.1'
},
// ─────────────────────────────────────────────────────────────────────────
// OAuth 2.1 Draft
// ─────────────────────────────────────────────────────────────────────────
OAUTH_2_1_CLIENT_CREDENTIALS: {
id: 'OAuth-2.1-client-credentials',
url: 'https://www.ietf.org/archive/id/draft-ietf-oauth-v2-1-13.html#section-4.2'
},
OAUTH_2_1_TOKEN_REQUEST: {
id: 'OAuth-2.1-token-request',
url: 'https://www.ietf.org/archive/id/draft-ietf-oauth-v2-1-13.html#name-token-request'
},
// ─────────────────────────────────────────────────────────────────────────
// MCP Authorization Specification (2025-06-18)
// ─────────────────────────────────────────────────────────────────────────
MCP_AUTH_SERVER_LOCATION: {
id: 'MCP-2025-06-18-server-location',
url: 'https://modelcontextprotocol.io/specification/2025-06-18/basic/authorization#authorization-server-location'
},
MCP_AUTH_PRM_DISCOVERY: {
id: 'MCP-2025-06-18-prm-discovery',
url: 'https://modelcontextprotocol.io/specification/2025-06-18/basic/authorization#authorization-server-location'
},
MCP_AUTH_SERVER_METADATA: {
id: 'MCP-2025-06-18-server-metadata',
url: 'https://modelcontextprotocol.io/specification/2025-06-18/basic/authorization#server-metadata-discovery'
},
MCP_AUTH_DCR: {
id: 'MCP-2025-06-18-dcr',
url: 'https://modelcontextprotocol.io/specification/2025-06-18/basic/authorization#dynamic-client-registration'
},
MCP_AUTH_ACCESS_TOKEN: {
id: 'MCP-2025-06-18-access-token',
url: 'https://modelcontextprotocol.io/specification/2025-06-18/basic/authorization#access-token-usage'
},
// ─────────────────────────────────────────────────────────────────────────
// MCP Extension: Client Credentials (SEP-1046)
// ─────────────────────────────────────────────────────────────────────────
SEP_1046_CLIENT_CREDENTIALS: {
id: 'SEP-1046-client-credentials',
url: 'https://github.com/modelcontextprotocol/ext-auth/blob/main/specification/draft/oauth-client-credentials.mdx'
}
};