This repository has been archived by the owner on Sep 11, 2024. It is now read-only.
[WIP] OIDC: Login #11093
Closed
[WIP] OIDC: Login #11093
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 29 commits
June 7, 2023 17:23
…rry/25468/oidc-client-registration
…rry/25468/oidc-client-registration
…dc-client-registration
…dc-client-registration
…dc-client-registration
Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
Base automatically changed from
kerry/25574/oidc-authorization-endpoint
to
develop
June 28, 2023 21:52
kerryarchibald
changed the base branch from
develop
to
kerry/25574/token-login-refactor
added 2 commits
June 29, 2023 14:16
|
Replaced by matrix-org/matrix-js-sdk#3554 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For element-hq/element-web#25657
With matrix-org/matrix-js-sdk#3499
With matrix-org/matrix-js-sdk#3531
Screen.Recording.2023-06-23.at.15.54.49.mov
3.1.1. Authorization Code Flow Steps
1. Client prepares an Authentication Request containing the desired request parameters.
2. Client sends the request to the Authorization Server.
3. Authorization Server Authenticates the End-User.
4. Authorization Server obtains End-User Consent/Authorization.
5. Authorization Server sends the End-User back to the Client with an Authorization Code.
6. Client requests a response using the Authorization Code at the Token Endpoint.
7. Client receives a response that contains an ID Token and Access Token in the response body.
8. Client validates the ID token and retrieves the End-User's Subject Identifier.
Checklist
Here's what your changelog entry will look like:
✨ Features