8000 [26.8] Fix External links check on release/26.8 by ssilvert · Pull Request #54769 · keycloak/keycloak · GitHub
[go: up one dir, main page]
Skip to content

[26.8] Fix External links check on release/26.8 #54769

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 3 commits into from
Nov 6, 2026
+5 −1
Merged

[26.8] Fix External links check on release/26.8 #54769

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
db14714
External links check fails due to Weblate
mabartos Nov 4, 2026
d51bdce
Ignore docs.redhat.com in the external links check
ssilvert Nov 6, 2026
595f1b0
Do not render auth.example.com as a link
ssilvert Nov 6, 2026
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
4 changes: 4 additions & 0 deletions docs/documentation/tests/src/test/resources/ignored-links
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -46,6 +46,10 @@ https://www.oasis-open.org/standard/saml/
https://www.h2database.com/*
# Blocks automated HTTP requests from CI runners (returns 403), but loads fine in a browser.
https://www.iso.org/*
# Blocks automated HTTP requests from CI runners (returns 403), but loads fine in a browser.
https://hosted.weblate.org/projects/keycloak/
# Blocks automated HTTP requests from CI runners (returns 403), but loads fine in a browser.
https://docs.redhat.com/*

# Remove after 26.8 release
https://www.keycloak.org/server/db#galera-cluster-considerations
Expand Down
2 changes: 1 addition & 1 deletion docs/documentation/upgrading/topics/changes/changes-26_8_2.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@ registration flow requires and add only those specific mapper types to BOTH the
To align with the OAuth 2.0 security recommendations (RFC 9700), the Admin REST API now verifies that bearer access tokens were issued specifically for the Admin API.
Previously, any access token was accepted regardless of its intended audience, as long as its subject had administrative access to the target realm, whether granted through realm admin roles or Fine-Grained Admin Permissions.

A new built-in client scope, `kc-admin-api`, provides this capability. The scope adds the realm's Admin REST API base URL (for example, `https://auth.example.com/admin/realms/my-realm`, resolved from the configured frontend URL)
A new built-in client scope, `kc-admin-api`, provides this capability. The scope adds the realm's Admin REST API base URL (for example, `+https://auth.example.com/admin/realms/my-realm+`, resolved from the configured frontend URL)
as an audience to the tokens issued for clients that have the scope.
The Admin REST API now requires the token to both carry this audience and include the `kc-admin-api` scope, so access is tied to this specific built-in scope rather than to any token that happens to carry a matching audience.
On upgrade, this client scope is created in every realm and assigned as a default client scope to the built-in clients used to access the Admin API (`admin-cli` and `security-admin-console`), so out-of-the-box access keeps working.
Expand Down
Loading
0