docs(security): add OAuth2/OIDC integration guide for Keycloak#733
Open
mihir-dixit2k27 wants to merge 1 commit into
Open
docs(security): add OAuth2/OIDC integration guide for Keycloak#733mihir-dixit2k27 wants to merge 1 commit into
mihir-dixit2k27 wants to merge 1 commit into
Conversation
kristin-kronstain-brown
requested changes
Jun 5, 2026
mihir-dixit2k27
force-pushed
the
docs/add-oauth2-oidc-keycloak-guide
branch
2 times, most recently
from
96c19fd to
83f9e7e
Compare
Add a new OAuth2/OIDC guide under the security section that walks through protecting an HTTPRoute using kgateway's built-in authorization code flow with Keycloak as the identity provider. Changes: - assets/docs/pages/security/oauth2-keycloak.md: full guide covering GatewayExtension setup, TrafficPolicy attachment, cookie configuration, and denyRedirect for API clients (401 instead of browser redirect) - content/docs/envoy/main/security/oauth2/_index.md: parent section page - content/docs/envoy/main/security/oauth2/keycloak.md: thin content file following the established reuse pattern - content/docs/envoy/main/security/_index.md: add OAuth2/OIDC card All field names (issuerURI, clientID, clientSecretRef, denyRedirect, endSessionEndpoint, cookies.names, cookies.sameSite) verified against gateway.kgateway.dev/v1alpha1 API reference. All shortcodes verified against existing guides. Hugo build confirmed no errors on new pages. Signed-off-by: Mihir Dixit <dixitmihir1@gmail.com>
mihir-dixit2k27
force-pushed
the
docs/add-oauth2-oidc-keycloak-guide
branch
from
83f9e7e to
1415cd2
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
kgateway has OAuth2/OIDC support but no how-to for it. This adds a Keycloak guide under the security section —
GatewayExtensionsetup,TrafficPolicyattachment, cookie config, anddenyRedirectso API clients get a401instead of a redirect to the Keycloak login page.Follows the same file/reuse pattern as the existing
extauth/basicandextauth/apikeyguides. All YAML field names checked against the API reference.Change Type
/kind documentation
Changelog
Additional Notes
Pre-existing blog build errors on
mainare unrelated to this PR — new pages build clean.Fixes #732