mirror of
https://github.com/0rangebananaspy/authelia.git
synced 2024-09-14 22:47:21 +07:00
196 lines
7.0 KiB
Markdown
196 lines
7.0 KiB
Markdown
---
|
|
title: "OpenID Connect"
|
|
description: "Authelia OpenID Connect Implementation"
|
|
lead: "The OpenID Connect Provider role is a very useful but complex feature to enhance interoperability of Authelia with other products. "
|
|
date: 2022-06-15T17:51:47+10:00
|
|
draft: false
|
|
images: []
|
|
menu:
|
|
roadmap:
|
|
parent: "active"
|
|
weight: 221
|
|
toc: true
|
|
aliases:
|
|
- /r/openid-connect
|
|
- /docs/roadmap/oidc.html
|
|
---
|
|
|
|
We have decided to implement [OpenID Connect] as a beta feature, it's suggested you only utilize it for testing and
|
|
providing feedback, and should take caution in relying on it in production as of now. [OpenID Connect] and it's related
|
|
endpoints are not enabled by default unless you specifically configure the [OpenID Connect] section.
|
|
|
|
As [OpenID Connect] is fairly complex (the [OpenID Connect] Provider role especially so) it's intentional that it is
|
|
both a beta and that the implemented features are part of a thoughtful roadmap. Items that are not immediately obvious
|
|
as required (i.e. bug fixes or spec features), will likely be discussed in team meetings or on GitHub issues before
|
|
being added to the list. We want to implement this feature in a very thoughtful way in order to avoid security issues.
|
|
|
|
## Stages
|
|
|
|
This section represents the stages involved in implementation of this feature. The stages are either in order of
|
|
implementation due to there being an underlying requirement to implement them in this order, or in a rough order due to
|
|
how important or difficult to implement they are.
|
|
|
|
### Beta 1
|
|
|
|
{{< roadmap-status stage="complete" version="v4.29.0" >}}
|
|
|
|
Feature List:
|
|
|
|
* [User Consent](https://openid.net/specs/openid-connect-core-1_0.html#Consent)
|
|
* [Authorization Code Flow](https://openid.net/specs/openid-connect-core-1_0.html#CodeFlowSteps)
|
|
* [OpenID Connect Discovery](https://openid.net/specs/openid-connect-discovery-1_0.html)
|
|
* [RS256 Signature Strategy](https://www.rfc-editor.org/rfc/rfc7518.html#section-3.1)
|
|
* Per Client Scope/Grant Type/Response Type Restriction
|
|
* Per Client Authorization Policy (1FA/2FA)
|
|
* Per Client List of Valid Redirection URI's
|
|
* [Confidential Client Type](https://www.rfc-editor.org/rfc/rfc6749.html#section-2.1)
|
|
|
|
### Beta 2
|
|
|
|
{{< roadmap-status stage="complete" version="v4.30.0" >}}
|
|
|
|
Feature List:
|
|
|
|
* [Userinfo Endpoint](https://openid.net/specs/openid-connect-core-1_0.html#UserInfo)
|
|
* Parameter Entropy
|
|
* Token/Code Lifespan
|
|
* Client Debug Messages
|
|
* Client Audience
|
|
* [Public Client Type](https://www.rfc-editor.org/rfc/rfc6749.html#section-2.1)
|
|
|
|
### Beta 3
|
|
|
|
{{< roadmap-status stage="complete" version="v4.34.0" >}}
|
|
|
|
Feature List:
|
|
|
|
* [Proof Key Code Exchange (PKCE)](https://www.rfc-editor.org/rfc/rfc7636.html) for Authorization Code Flow
|
|
* Claims:
|
|
* `preferred_username` - sending the username in this claim instead of the `sub` claim.
|
|
|
|
### Beta 4
|
|
|
|
{{< roadmap-status stage="complete" version="v4.35.0" >}}
|
|
|
|
Feature List:
|
|
|
|
* Persistent Storage
|
|
* Tokens
|
|
* Auditable Information
|
|
* Subject to User Mapping
|
|
* Opaque [RFC4122] UUID v4's for subject identifiers
|
|
* Support for Pairwise and Plain subject identifier types as per [OpenID Connect Core (Subject Identifier Types)]
|
|
* Utilize the pairwise example method 3 as per [OpenID Connect Core (Pairwise Identifier Algorithm)]
|
|
* Claims:
|
|
* `sub` - replace username with opaque random [RFC4122] UUID v4
|
|
* `amr` - authentication method references as per [RFC8176]
|
|
* `azp` - authorized party as per [OpenID Connect Core (ID Token)]
|
|
* `client_id` - the Client ID as per [RFC8693 Section 4.3]
|
|
* [Cross Origin Resource Sharing] (CORS):
|
|
* Automatically allow all cross-origin requests to the discovery endpoints
|
|
* Automatically allow all cross-origin requests to the JSON Web Keys endpoint
|
|
* Optionally allow cross-origin requests to the other endpoints individually
|
|
|
|
### Beta 5
|
|
|
|
{{< roadmap-status >}}
|
|
|
|
Feature List:
|
|
|
|
* Prompt Handling
|
|
* Display Handling
|
|
|
|
See [OpenID Connect Core (Mandatory to Implement Features for All OpenID Providers)].
|
|
|
|
### Beta 6
|
|
|
|
{{< roadmap-status >}}
|
|
|
|
Feature List:
|
|
|
|
* Revoke Tokens on User Logout or Expiration
|
|
* [JSON Web Key Rotation](https://openid.net/specs/openid-connect-messages-1_0-20.html#rotate.sig.keys)
|
|
* Hashed Client Secrets
|
|
|
|
### General Availability
|
|
|
|
{{< roadmap-status >}}
|
|
|
|
Feature List:
|
|
|
|
* Enable by Default
|
|
* Only after all previous stages are checked for bugs
|
|
|
|
### Miscellaneous
|
|
|
|
This stage lists features which individually do not fit into a specific stage and may or may not be implemented.
|
|
|
|
#### OpenID Connect Dynamic Client Registration
|
|
|
|
{{< roadmap-status >}}
|
|
|
|
See the [OpenID Connect] website for the [OpenID Connect Dynamic Client Registration] specification.
|
|
|
|
#### OpenID Connect Back-Channel Logout
|
|
|
|
{{< roadmap-status >}}
|
|
|
|
See the [OpenID Connect] website for the [OpenID Connect Back-Channel Logout] specification.
|
|
|
|
Should be implemented alongside [Dynamic Client Registration](#openid-connect-dynamic-client-registration).
|
|
|
|
#### OpenID Connect Front-Channel Logout
|
|
|
|
{{< roadmap-status >}}
|
|
|
|
See the [OpenID Connect] website for the [OpenID Connect Front-Channel Logout] specification.
|
|
|
|
Should be implemented alongside [Dynamic Client Registration](#openid-connect-dynamic-client-registration).
|
|
|
|
#### OAuth 2.0 Authorization Server Metadata
|
|
|
|
{{< roadmap-status stage="complete" version="v4.34.0" >}}
|
|
|
|
See the [IETF Specification RFC8414](https://www.rfc-editor.org/rfc/rfc8414.html) for more information.
|
|
|
|
#### OpenID Connect Session Management
|
|
|
|
{{< roadmap-status >}}
|
|
|
|
See the [OpenID Connect] website for the [OpenID Connect Session Management] specification.
|
|
|
|
#### End-User Scope Grants
|
|
|
|
{{< roadmap-status >}}
|
|
|
|
Allow users to choose which scopes they grant.
|
|
|
|
#### Client RBAC
|
|
|
|
{{< roadmap-status >}}
|
|
|
|
Allow clients to be configured with a list of users and groups who have access to them.
|
|
|
|
#### Preferred Username Claim
|
|
|
|
{{< roadmap-status stage="complete" version="v4.33.2" >}}
|
|
|
|
The `preferred_username` claim was missing and was fixed.
|
|
|
|
[Cross Origin Resource Sharing]: https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS
|
|
|
|
[RFC8176]: https://www.rfc-editor.org/rfc/rfc8176.html
|
|
[RFC8693 Section 4.3]: https://www.rfc-editor.org/rfc/rfc8693.html/#section-4.3
|
|
[RFC4122]: https://www.rfc-editor.org/rfc/rfc4122.html
|
|
|
|
[OpenID Connect]: https://openid.net/connect/
|
|
[OpenID Connect Front-Channel Logout]: https://openid.net/specs/openid-connect-frontchannel-1_0.html
|
|
[OpenID Connect Back-Channel Logout]: https://openid.net/specs/openid-connect-backchannel-1_0.html
|
|
[OpenID Connect Session Management]: https://openid.net/specs/openid-connect-session-1_0.html
|
|
[OpenID Connect Dynamic Client Registration]: https://openid.net/specs/openid-connect-registration-1_0.html
|
|
|
|
[OpenID Connect Core (ID Token)]: https://openid.net/specs/openid-connect-core-1_0.html#IDToken
|
|
[OpenID Connect Core (Subject Identifier Types)]: https://openid.net/specs/openid-connect-core-1_0.html#SubjectIDTypes
|
|
[OpenID Connect Core (Pairwise Identifier Algorithm)]: https://openid.net/specs/openid-connect-core-1_0.html#PairwiseAlg
|
|
[OpenID Connect Core (Mandatory to Implement Features for All OpenID Providers)]: https://openid.net/specs/openid-connect-core-1_0.html#ServerMTI
|