Repository navigation
Conversation
A new optional mobile section (enabled, redirectUri, postLogoutRedirectUri, both URIs defaulting to org.libredb.mobile:/oauth2redirect) lets an operator turn on the LibreDB mobile app. When enabled, keycloak-configure converges the public client libredb-mobile: standard flow with PKCE S256 only, the default scopes basic, profile, email and libredb-roles, and a client audience mapper that adds libredb-studio-api to the access token. The planner gains client-level mapper actions, and a new client no longer gets PUTs for scopes the realm already gives it. studio.env gets OIDC_BEARER_AUDIENCE and OIDC_BEARER_CLIENT_IDS under the new inventory condition mobileClient. The export, the manual realm check and the docs cover the client, and the docs note that the bearer channel needs a Studio release with libredb-studio#1914. With the section absent or disabled, the normalized config, the Keycloak plan, the export, studio.env and the step input hash stay unchanged.
15 of 19 tasks
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.
Lets an install serve the LibreDB mobile app (libredb/libredb-mobile#1), which calls Studio with a Keycloak access token through Studio's bearer channel (libredb/libredb-studio#1914).
With
mobile.enabled: trueinlibredb.yamlthe installer converges a public clientlibredb-mobile(standard flow, PKCE S256, scopesbasic,profile,email,libredb-roles, an audience mapper addinglibredb-studio-apito the access token) and gives StudioOIDC_BEARER_AUDIENCEandOIDC_BEARER_CLIENT_IDS. The export, the manual realm check and the docs cover it. Absent or disabled, the config, plan, export andstudio.envare unchanged.Verified:
bun run typecheck,bun run test(846 pass), coverage check, build, and the Keycloak 26.8.1 integration tests, including a real PKCE login aslibredb-mobilethat checksaud,azp,libredb_rolesand the refused password grant.Not verified: a full install against Studio, since no Studio release has #1914 yet; the pinned Studio 1.0.0 lacks it, so the version bump waits for that release.