/
types.go
568 lines (496 loc) · 25.3 KB
/
types.go
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
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
package oidc
import (
"crypto/rsa"
"time"
"github.com/ory/fosite"
"github.com/ory/fosite/handler/openid"
"github.com/ory/fosite/token/jwt"
"github.com/ory/herodot"
"gopkg.in/square/go-jose.v2"
"github.com/authelia/authelia/v4/internal/authorization"
"github.com/authelia/authelia/v4/internal/model"
"github.com/authelia/authelia/v4/internal/storage"
"github.com/authelia/authelia/v4/internal/utils"
)
// NewSession creates a new empty OpenIDSession struct.
func NewSession() (session *model.OpenIDSession) {
return &model.OpenIDSession{
DefaultSession: &openid.DefaultSession{
Claims: &jwt.IDTokenClaims{
Extra: map[string]interface{}{},
},
Headers: &jwt.Headers{
Extra: map[string]interface{}{},
},
},
Extra: map[string]interface{}{},
}
}
// NewSessionWithAuthorizeRequest uses details from an AuthorizeRequester to generate an OpenIDSession.
func NewSessionWithAuthorizeRequest(issuer, kid, username string, amr []string, extra map[string]interface{},
authTime time.Time, consent *model.OAuth2ConsentSession, requester fosite.AuthorizeRequester) (session *model.OpenIDSession) {
if extra == nil {
extra = make(map[string]interface{})
}
session = &model.OpenIDSession{
DefaultSession: &openid.DefaultSession{
Claims: &jwt.IDTokenClaims{
Subject: consent.Subject.UUID.String(),
Issuer: issuer,
AuthTime: authTime,
RequestedAt: consent.RequestedAt,
IssuedAt: time.Now(),
Nonce: requester.GetRequestForm().Get("nonce"),
Audience: requester.GetGrantedAudience(),
Extra: extra,
AuthenticationMethodsReferences: amr,
},
Headers: &jwt.Headers{
Extra: map[string]interface{}{
"kid": kid,
},
},
Subject: consent.Subject.UUID.String(),
Username: username,
},
Extra: map[string]interface{}{},
ClientID: requester.GetClient().GetID(),
ChallengeID: consent.ChallengeID,
}
// Ensure required audience value of the client_id exists.
if !utils.IsStringInSlice(requester.GetClient().GetID(), session.Claims.Audience) {
session.Claims.Audience = append(session.Claims.Audience, requester.GetClient().GetID())
}
session.Claims.Add("azp", session.ClientID)
session.Claims.Add("client_id", session.ClientID)
return session
}
// OpenIDConnectProvider for OpenID Connect.
type OpenIDConnectProvider struct {
Fosite fosite.OAuth2Provider
Store *OpenIDConnectStore
KeyManager *KeyManager
herodot *herodot.JSONWriter
discovery OpenIDConnectWellKnownConfiguration
}
// OpenIDConnectStore is Authelia's internal representation of the fosite.Storage interface. It maps the following
// interfaces to the storage.Provider interface:
// fosite.Storage, fosite.ClientManager, storage.Transactional, oauth2.AuthorizeCodeStorage, oauth2.AccessTokenStorage,
// oauth2.RefreshTokenStorage, oauth2.TokenRevocationStorage, pkce.PKCERequestStorage,
// openid.OpenIDConnectRequestStorage, and partially implements rfc7523.RFC7523KeyStorage.
type OpenIDConnectStore struct {
provider storage.Provider
clients map[string]*Client
}
// Client represents the client internally.
type Client struct {
ID string
Description string
Secret []byte
SectorIdentifier string
Public bool
Audience []string
Scopes []string
RedirectURIs []string
GrantTypes []string
ResponseTypes []string
ResponseModes []fosite.ResponseModeType
UserinfoSigningAlgorithm string
Policy authorization.Level
PreConfiguredConsentDuration *time.Duration
}
// KeyManager keeps track of all of the active/inactive rsa keys and provides them to services requiring them.
// It additionally allows us to add keys for the purpose of key rotation in the future.
type KeyManager struct {
activeKeyID string
keys map[string]*rsa.PrivateKey
keySet *jose.JSONWebKeySet
strategy *RS256JWTStrategy
}
// PlainTextHasher implements the fosite.Hasher interface without an actual hashing algo.
type PlainTextHasher struct{}
// ConsentGetResponseBody schema of the response body of the consent GET endpoint.
type ConsentGetResponseBody struct {
ClientID string `json:"client_id"`
ClientDescription string `json:"client_description"`
Scopes []string `json:"scopes"`
Audience []string `json:"audience"`
PreConfiguration bool `json:"pre_configuration"`
}
// ConsentPostRequestBody schema of the request body of the consent POST endpoint.
type ConsentPostRequestBody struct {
ClientID string `json:"client_id"`
ConsentID string `json:"consent_id"`
Consent bool `json:"consent"`
PreConfigure bool `json:"pre_configure"`
}
// ConsentPostResponseBody schema of the response body of the consent POST endpoint.
type ConsentPostResponseBody struct {
RedirectURI string `json:"redirect_uri"`
}
/*
CommonDiscoveryOptions represents the discovery options used in both OAuth 2.0 and OpenID Connect.
See Also:
OpenID Connect Discovery: https://openid.net/specs/openid-connect-discovery-1_0.html#ProviderMetadata
OAuth 2.0 Discovery: https://datatracker.ietf.org/doc/html/draft-ietf-oauth-discovery-10#section-2
*/
type CommonDiscoveryOptions struct {
/*
REQUIRED. URL using the https scheme with no query or fragment component that the OP asserts as its Issuer
Identifier. If Issuer discovery is supported (see Section 2), this value MUST be identical to the issuer value
returned by WebFinger. This also MUST be identical to the iss Claim value in ID Tokens issued from this Issuer.
*/
Issuer string `json:"issuer"`
/*
REQUIRED. URL of the OP's JSON Web Key Set [JWK] document. This contains the signing key(s) the RP uses to
validate signatures from the OP. The JWK Set MAY also contain the Server's encryption key(s), which are used by
RPs to encrypt requests to the Server. When both signing and encryption keys are made available, a use (Key Use)
parameter value is REQUIRED for all keys in the referenced JWK Set to indicate each key's intended usage.
Although some algorithms allow the same key to be used for both signatures and encryption, doing so is NOT
RECOMMENDED, as it is less secure. The JWK x5c parameter MAY be used to provide X.509 representations of keys
provided. When used, the bare key values MUST still be present and MUST match those in the certificate.
*/
JWKSURI string `json:"jwks_uri,omitempty"`
/*
REQUIRED. URL of the OP's OAuth 2.0 Authorization Endpoint [OpenID.Core].
See Also:
OpenID.Core: https://openid.net/specs/openid-connect-core-1_0.html
*/
AuthorizationEndpoint string `json:"authorization_endpoint"`
/*
URL of the OP's OAuth 2.0 Token Endpoint [OpenID.Core]. This is REQUIRED unless only the Implicit Flow is used.
See Also:
OpenID.Core: https://openid.net/specs/openid-connect-core-1_0.html
*/
TokenEndpoint string `json:"token_endpoint,omitempty"`
/*
REQUIRED. JSON array containing a list of the Subject Identifier types that this OP supports. Valid types
include pairwise and public.
*/
SubjectTypesSupported []string `json:"subject_types_supported"`
/*
REQUIRED. JSON array containing a list of the OAuth 2.0 response_type values that this OP supports. Dynamic
OpenID Providers MUST support the code, id_token, and the token id_token Response Type values.
*/
ResponseTypesSupported []string `json:"response_types_supported"`
/*
OPTIONAL. JSON array containing a list of the OAuth 2.0 Grant Type values that this OP supports. Dynamic OpenID
Providers MUST support the authorization_code and implicit Grant Type values and MAY support other Grant Types.
If omitted, the default value is ["authorization_code", "implicit"].
*/
GrantTypesSupported []string `json:"grant_types_supported,omitempty"`
/*
OPTIONAL. JSON array containing a list of the OAuth 2.0 response_mode values that this OP supports, as specified
in OAuth 2.0 Multiple Response Type Encoding Practices [OAuth.Responses]. If omitted, the default for Dynamic
OpenID Providers is ["query", "fragment"].
*/
ResponseModesSupported []string `json:"response_modes_supported,omitempty"`
/*
RECOMMENDED. JSON array containing a list of the OAuth 2.0 [RFC6749] scope values that this server supports.
The server MUST support the openid scope value. Servers MAY choose not to advertise some supported scope values
even when this parameter is used, although those defined in [OpenID.Core] SHOULD be listed, if supported.
See Also:
OAuth 2.0: https://datatracker.ietf.org/doc/html/rfc6749
OpenID.Core: https://openid.net/specs/openid-connect-core-1_0.html
*/
ScopesSupported []string `json:"scopes_supported,omitempty"`
/*
RECOMMENDED. JSON array containing a list of the Claim Names of the Claims that the OpenID Provider MAY be able
to supply values for. Note that for privacy or other reasons, this might not be an exhaustive list.
*/
ClaimsSupported []string `json:"claims_supported,omitempty"`
/*
OPTIONAL. Languages and scripts supported for the user interface, represented as a JSON array of BCP47 [RFC5646]
language tag values.
See Also:
BCP47: https://datatracker.ietf.org/doc/html/rfc5646
*/
UILocalesSupported []string `json:"ui_locales_supported,omitempty"`
/*
OPTIONAL. JSON array containing a list of Client Authentication methods supported by this Token Endpoint. The
options are client_secret_post, client_secret_basic, client_secret_jwt, and private_key_jwt, as described in
Section 9 of OpenID Connect Core 1.0 [OpenID.Core]. Other authentication methods MAY be defined by extensions.
If omitted, the default is client_secret_basic -- the HTTP Basic Authentication Scheme specified in Section
2.3.1 of OAuth 2.0 [RFC6749].
See Also:
OAuth 2.0: https://datatracker.ietf.org/doc/html/rfc6749
OpenID.Core Section 9: https://openid.net/specs/openid-connect-core-1_0.html#ClientAuthentication
*/
TokenEndpointAuthMethodsSupported []string `json:"token_endpoint_auth_methods_supported,omitempty"`
/*
OPTIONAL. JSON array containing a list of the JWS signing algorithms (alg values) supported by the Token Endpoint
for the signature on the JWT [JWT] used to authenticate the Client at the Token Endpoint for the private_key_jwt
and client_secret_jwt authentication methods. Servers SHOULD support RS256. The value none MUST NOT be used.
See Also:
JWT: https://datatracker.ietf.org/doc/html/rfc7519
*/
TokenEndpointAuthSigningAlgValuesSupported []string `json:"token_endpoint_auth_signing_alg_values_supported,omitempty"`
/*
OPTIONAL. URL of a page containing human-readable information that developers might want or need to know when
using the OpenID Provider. In particular, if the OpenID Provider does not support Dynamic Client Registration,
then information on how to register Clients needs to be provided in this documentation.
*/
ServiceDocumentation string `json:"service_documentation,omitempty"`
/*
OPTIONAL. URL that the OpenID Provider provides to the person registering the Client to read about the OP's
requirements on how the Relying Party can use the data provided by the OP. The registration process SHOULD
display this URL to the person registering the Client if it is given.
*/
OPPolicyURI string `json:"op_policy_uri,omitempty"`
/*
OPTIONAL. URL that the OpenID Provider provides to the person registering the Client to read about OpenID
Provider's terms of service. The registration process SHOULD display this URL to the person registering the
Client if it is given.
*/
OPTOSURI string `json:"op_tos_uri,omitempty"`
}
// OAuth2DiscoveryOptions represents the discovery options specific to OAuth 2.0.
type OAuth2DiscoveryOptions struct {
/*
OPTIONAL. URL of the authorization server's OAuth 2.0 introspection endpoint [RFC7662].
See Also:
OAuth 2.0 Token Introspection: https://datatracker.ietf.org/doc/html/rfc7662
*/
IntrospectionEndpoint string `json:"introspection_endpoint,omitempty"`
/*
OPTIONAL. URL of the authorization server's OAuth 2.0 revocation endpoint [RFC7009].
See Also:
OAuth 2.0 Token Revocation: https://datatracker.ietf.org/doc/html/rfc7009
*/
RevocationEndpoint string `json:"revocation_endpoint,omitempty"`
/*
OPTIONAL. URL of the authorization server's OAuth 2.0 Dynamic Client Registration endpoint [RFC7591].
See Also:
OAuth 2.0 Dynamic Client Registration Protocol: https://datatracker.ietf.org/doc/html/rfc7591
*/
RegistrationEndpoint string `json:"registration_endpoint,omitempty"`
/*
OPTIONAL. JSON array containing a list of client authentication methods supported by this introspection endpoint.
The valid client authentication method values are those registered in the IANA "OAuth Token Endpoint
Authentication Methods" registry [IANA.OAuth.Parameters] or those registered in the IANA "OAuth Access Token Types"
registry [IANA.OAuth.Parameters]. (These values are and will remain distinct, due to Section 7.2.) If omitted,
the set of supported authentication methods MUST be determined by other means.
See Also:
IANA.OAuth.Parameters: https://www.iana.org/assignments/oauth-parameters/oauth-parameters.xhtml
OAuth 2.0 Authorization Server Metadata - Updated Registration Instructions: https://datatracker.ietf.org/doc/html/draft-ietf-oauth-discovery-10#section-7.2
*/
IntrospectionEndpointAuthMethodsSupported []string `json:"introspection_endpoint_auth_methods_supported,omitempty"`
/*
OPTIONAL. JSON array containing a list of client authentication methods supported by this revocation endpoint.
The valid client authentication method values are those registered in the IANA "OAuth Token Endpoint
Authentication Methods" registry [IANA.OAuth.Parameters]. If omitted, the default is "client_secret_basic" --
the HTTP Basic Authentication Scheme specified in Section 2.3.1 of OAuth 2.0 [RFC6749].
See Also:
IANA.OAuth.Parameters: https://www.iana.org/assignments/oauth-parameters/oauth-parameters.xhtml
OAuth 2.0 - Client Password: https://datatracker.ietf.org/doc/html/rfc6749#section-2.3.1
*/
RevocationEndpointAuthMethodsSupported []string `json:"revocation_endpoint_auth_methods_supported,omitempty"`
/*
OPTIONAL. JSON array containing a list of the JWS signing algorithms ("alg" values) supported by the revocation
endpoint for the signature on the JWT [JWT] used to authenticate the client at the revocation endpoint for the
"private_key_jwt" and "client_secret_jwt" authentication methods. This metadata entry MUST be present if either
of these authentication methods are specified in the "revocation_endpoint_auth_methods_supported" entry. No
default algorithms are implied if this entry is omitted. The value "none" MUST NOT be used.
See Also:
JWT: https://datatracker.ietf.org/doc/html/rfc7519
*/
RevocationEndpointAuthSigningAlgValuesSupported []string `json:"revocation_endpoint_auth_signing_alg_values_supported,omitempty"`
/*
OPTIONAL. JSON array containing a list of the JWS signing algorithms ("alg" values) supported by the
introspection endpoint for the signature on the JWT [JWT] used to authenticate the client at the introspection
endpoint for the "private_key_jwt" and "client_secret_jwt" authentication methods. This metadata entry MUST be
present if either of these authentication methods are specified in the
"introspection_endpoint_auth_methods_supported" entry. No default algorithms are implied if this entry is omitted.
The value "none" MUST NOT be used.
See Also:
JWT: https://datatracker.ietf.org/doc/html/rfc7519
*/
IntrospectionEndpointAuthSigningAlgValuesSupported []string `json:"introspection_endpoint_auth_signing_alg_values_supported,omitempty"`
/*
OPTIONAL. JSON array containing a list of PKCE [RFC7636] code challenge methods supported by this authorization
server. Code challenge method values are used in the "code_challenge_method" parameter defined in Section 4.3 of
[RFC7636]. The valid code challenge method values are those registered in the IANA "PKCE Code Challenge Methods"
registry [IANA.OAuth.Parameters]. If omitted, the authorization server does not support PKCE.
See Also:
PKCE: https://datatracker.ietf.org/doc/html/rfc7636
IANA.OAuth.Parameters: https://www.iana.org/assignments/oauth-parameters/oauth-parameters.xhtml
*/
CodeChallengeMethodsSupported []string `json:"code_challenge_methods_supported,omitempty"`
}
// OpenIDConnectDiscoveryOptions represents the discovery options specific to OpenID Connect.
type OpenIDConnectDiscoveryOptions struct {
/*
RECOMMENDED. URL of the OP's UserInfo Endpoint [OpenID.Core]. This URL MUST use the https scheme and MAY contain
port, path, and query parameter components.
See Also:
OpenID.Core: https://openid.net/specs/openid-connect-core-1_0.html
*/
UserinfoEndpoint string `json:"userinfo_endpoint,omitempty"`
/*
REQUIRED. JSON array containing a list of the JWS signing algorithms (alg values) supported by the OP for the ID
Token to encode the Claims in a JWT [JWT]. The algorithm RS256 MUST be included. The value none MAY be supported,
but MUST NOT be used unless the Response Type used returns no ID Token from the Authorization Endpoint (such as
when using the Authorization Code Flow).
See Also:
JWT: https://datatracker.ietf.org/doc/html/rfc7519
*/
IDTokenSigningAlgValuesSupported []string `json:"id_token_signing_alg_values_supported,omitempty"`
/*
OPTIONAL. JSON array containing a list of the JWS [JWS] signing algorithms (alg values) [JWA] supported by the
UserInfo Endpoint to encode the Claims in a JWT [JWT]. The value none MAY be included.
See Also:
JWS: https://datatracker.ietf.org/doc/html/rfc7515
JWA: https://datatracker.ietf.org/doc/html/rfc7518
JWT: https://datatracker.ietf.org/doc/html/rfc7519
*/
UserinfoSigningAlgValuesSupported []string `json:"userinfo_signing_alg_values_supported,omitempty"`
/*
OPTIONAL. JSON array containing a list of the JWS signing algorithms (alg values) supported by the OP for Request
Objects, which are described in Section 6.1 of OpenID Connect Core 1.0 [OpenID.Core]. These algorithms are used
both when the Request Object is passed by value (using the request parameter) and when it is passed by reference
(using the request_uri parameter). Servers SHOULD support none and RS256.
*/
RequestObjectSigningAlgValuesSupported []string `json:"request_object_signing_alg_values_supported,omitempty"`
/*
OPTIONAL. JSON array containing a list of the JWE encryption algorithms (alg values) supported by the OP for the
ID Token to encode the Claims in a JWT [JWT].
See Also:
JWE: https://datatracker.ietf.org/doc/html/rfc7516
JWT: https://datatracker.ietf.org/doc/html/rfc7519
*/
IDTokenEncryptionAlgValuesSupported []string `json:"id_token_encryption_alg_values_supported,omitempty"`
/*
OPTIONAL. JSON array containing a list of the JWE [JWE] encryption algorithms (alg values) [JWA] supported by
the UserInfo Endpoint to encode the Claims in a JWT [JWT].
See Also:
JWE: https://datatracker.ietf.org/doc/html/rfc7516
JWA: https://datatracker.ietf.org/doc/html/rfc7518
JWT: https://datatracker.ietf.org/doc/html/rfc7519
*/
UserinfoEncryptionAlgValuesSupported []string `json:"userinfo_encryption_alg_values_supported,omitempty"`
/*
OPTIONAL. JSON array containing a list of the JWE encryption algorithms (alg values) supported by the OP for
Request Objects. These algorithms are used both when the Request Object is passed by value and when it is passed
by reference.
See Also:
JWE: https://datatracker.ietf.org/doc/html/rfc7516
*/
RequestObjectEncryptionAlgValuesSupported []string `json:"request_object_encryption_alg_values_supported,omitempty"`
/*
OPTIONAL. JSON array containing a list of the JWE encryption algorithms (enc values) supported by the OP for the
ID Token to encode the Claims in a JWT [JWT].
See Also:
JWE: https://datatracker.ietf.org/doc/html/rfc7516
JWT: https://datatracker.ietf.org/doc/html/rfc7519
*/
IDTokenEncryptionEncValuesSupported []string `json:"id_token_encryption_enc_values_supported,omitempty"`
/*
OPTIONAL. JSON array containing a list of the JWE encryption algorithms (enc values) [JWA] supported by the
UserInfo Endpoint to encode the Claims in a JWT [JWT].
See Also:
JWE: https://datatracker.ietf.org/doc/html/rfc7516
JWA: https://datatracker.ietf.org/doc/html/rfc7518
JWT: https://datatracker.ietf.org/doc/html/rfc7519
*/
UserinfoEncryptionEncValuesSupported []string `json:"userinfo_encryption_enc_values_supported,omitempty"`
/*
OPTIONAL. JSON array containing a list of the JWE encryption algorithms (enc values) supported by the OP for
Request Objects. These algorithms are used both when the Request Object is passed by value and when it is passed
by reference.
See Also:
JWE: https://datatracker.ietf.org/doc/html/rfc7516
JWT: https://datatracker.ietf.org/doc/html/rfc7519
*/
RequestObjectEncryptionEncValuesSupported []string `json:"request_object_encryption_enc_values_supported,omitempty"`
/*
OPTIONAL. JSON array containing a list of the Authentication Context Class References that this OP supports.
*/
ACRValuesSupported []string `json:"acr_values_supported,omitempty"`
/*
OPTIONAL. JSON array containing a list of the display parameter values that the OpenID Provider supports. These
values are described in Section 3.1.2.1 of OpenID Connect Core 1.0 [OpenID.Core].
See Also:
OpenID.Core Section 3.1.2.1: https://openid.net/specs/openid-connect-core-1_0.html#AuthRequest
*/
DisplayValuesSupported []string `json:"display_values_supported,omitempty"`
/*
OPTIONAL. JSON array containing a list of the Claim Types that the OpenID Provider supports. These Claim Types
are described in Section 5.6 of OpenID Connect Core 1.0 [OpenID.Core]. Values defined by this specification are
normal, aggregated, and distributed. If omitted, the implementation supports only normal Claims.
See Also:
OpenID.Core Section 5.6: https://openid.net/specs/openid-connect-core-1_0.html#ClaimTypes
*/
ClaimTypesSupported []string `json:"claim_types_supported,omitempty"`
/*
OPTIONAL. Languages and scripts supported for values in Claims being returned, represented as a JSON array of
BCP47 [RFC5646] language tag values. Not all languages and scripts are necessarily supported for all Claim values.
See Also:
BCP47: https://datatracker.ietf.org/doc/html/rfc5646
*/
ClaimLocalesSupported []string `json:"claims_locales_supported,omitempty"`
/*
OPTIONAL. Boolean value specifying whether the OP supports use of the request_uri parameter, with true indicating
support. If omitted, the default value is true.
*/
RequestURIParameterSupported bool `json:"request_uri_parameter_supported"`
/*
OPTIONAL. Boolean value specifying whether the OP requires any request_uri values used to be pre-registered using
the request_uris registration parameter. Pre-registration is REQUIRED when the value is true. If omitted, the
default value is false.
*/
RequireRequestURIRegistration bool `json:"require_request_uri_registration"`
/*
OPTIONAL. Boolean value specifying whether the OP supports use of the claims parameter, with true indicating
support. If omitted, the default value is false.
*/
ClaimsParameterSupported bool `json:"claims_parameter_supported"`
}
// OpenIDConnectFrontChannelLogoutDiscoveryOptions represents the discovery options specific to
// OpenID Connect Front-Channel Logout functionality.
// See Also:
//
// OpenID Connect Front-Channel Logout: https://openid.net/specs/openid-connect-frontchannel-1_0.html#OPLogout
type OpenIDConnectFrontChannelLogoutDiscoveryOptions struct {
/*
OPTIONAL. Boolean value specifying whether the OP supports HTTP-based logout, with true indicating support. If
omitted, the default value is false.
*/
FrontChannelLogoutSupported bool `json:"frontchannel_logout_supported"`
/*
OPTIONAL. Boolean value specifying whether the OP can pass iss (issuer) and sid (session ID) query parameters to
identify the RP session with the OP when the frontchannel_logout_uri is used. If supported, the sid Claim is also
included in ID Tokens issued by the OP. If omitted, the default value is false.
*/
FrontChannelLogoutSessionSupported bool `json:"frontchannel_logout_session_supported"`
}
// OpenIDConnectBackChannelLogoutDiscoveryOptions represents the discovery options specific to
// OpenID Connect Back-Channel Logout functionality.
// See Also:
//
// OpenID Connect Back-Channel Logout: https://openid.net/specs/openid-connect-backchannel-1_0.html#BCSupport
type OpenIDConnectBackChannelLogoutDiscoveryOptions struct {
/*
OPTIONAL. Boolean value specifying whether the OP supports back-channel logout, with true indicating support.
If omitted, the default value is false.
*/
BackChannelLogoutSupported bool `json:"backchannel_logout_supported"`
/*
OPTIONAL. Boolean value specifying whether the OP can pass a sid (session ID) Claim in the Logout Token to
identify the RP session with the OP. If supported, the sid Claim is also included in ID Tokens issued by the OP.
If omitted, the default value is false.
*/
BackChannelLogoutSessionSupported bool `json:"backchannel_logout_session_supported"`
}
// OAuth2WellKnownConfiguration represents the well known discovery document specific to OAuth 2.0.
type OAuth2WellKnownConfiguration struct {
CommonDiscoveryOptions
OAuth2DiscoveryOptions
}
// OpenIDConnectWellKnownConfiguration represents the well known discovery document specific to OpenID Connect.
type OpenIDConnectWellKnownConfiguration struct {
CommonDiscoveryOptions
OAuth2DiscoveryOptions
OpenIDConnectDiscoveryOptions
OpenIDConnectFrontChannelLogoutDiscoveryOptions
OpenIDConnectBackChannelLogoutDiscoveryOptions
}