docs(analytics): PLTF-3531 add Keycloak auth values for Laminar Helm install - #775
Open
aivong-openhands wants to merge 2 commits into
Open
docs(analytics): PLTF-3531 add Keycloak auth values for Laminar Helm install#775aivong-openhands wants to merge 2 commits into
aivong-openhands wants to merge 2 commits into
Conversation
Add the Keycloak auth values (nextauthUrl/nextPublicUrl plus AUTH_KEYCLOAK_ID/ SECRET/ISSUER sourced from the chart-managed keycloak-realm Secret) to the Kubernetes (Helm) Laminar frontend example, and document the Keycloak client redirect URI / web origin required for the Continue with Keycloak flow. Co-authored-by: openhands <openhands@all-hands.dev>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
aivong-openhands
changed the title
Co-authored-by: openhands <openhands@all-hands.dev>
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
1 participant
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.
Summary of changes
Enabling Laminar analytics through Helm previously left authentication unconfigured, so the Continue with Keycloak button on the self-hosted Laminar UI had no working provider and login failed. This documents the values that point the Laminar frontend at the same Keycloak realm as OpenHands Enterprise, in the Kubernetes (Helm) tab of the Analytics page.
laminar.frontend, addsnextauthUrl/nextPublicUrland theAUTH_KEYCLOAK_ID/AUTH_KEYCLOAK_SECRET/AUTH_KEYCLOAK_ISSUERenv, with the client id and secret sourced from the chart-managedkeycloak-realmSecret and the issuer pointing at theallhandsrealm.Invalid parameter: redirect_uri.Verified against a live OpenHands Enterprise Helm deployment: the documented values produce a working Keycloak login, and the redirect-URI note reproduces the exact failure it warns about. Every value uses a generic placeholder, so no environment-specific hostnames or secrets appear in the page.
This PR was drafted by an AI agent on behalf of the user.