8000 Use datatracker.ietf.org instead of www.rfc-editor.org for specs by rmartinc · Pull Request #49291 · keycloak/keycloak · GitHub
[go: up one dir, main page]
Skip to content

Use datatracker.ietf.org instead of www.rfc-editor.org for specs #49291

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ahus1 merged 1 commit into from
May 26, 2026
Merged

Use datatracker.ietf.org instead of www.rfc-editor.org for specs #49291

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/documentation/upgrading/topics/changes/changes-21_1_0.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ Default `Client ID` mapper of `Service Account Client` has been changed. `Token
`client_id` claim is compliant with OAuth2 specifications:

- https://datatracker.ietf.org/doc/html/rfc9068#section-2.2[JSON Web Token (JWT) Profile for OAuth 2.0 Access Tokens]
- https://www.rfc-editor.org/rfc/rfc7662#section-2.2[OAuth 2.0 Token Introspection]
- https://datatracker.ietf.org/doc/html/rfc7662#section-2.2[OAuth 2.0 Token Introspection]
- https://datatracker.ietf.org/doc/html/rfc8693#section-4.3[OAuth 2.0 Token Exchange]

`clientId` userSession note still exists.
Expand Down
0