Skip to content

Conversation

@PovilasID
Copy link

To make Keycloak work with gramps there are a couple of settings changes that deviate from most common defaults this points them out.

@DavidMStraub
Copy link
Member

DavidMStraub commented Nov 19, 2025

Thanks a lot!

I piped your addition through Lumo AI to smooth out some minor grammar slips. What do you think?

Keycloak

Most of the configuration for Keycloak can be left at its defaults (Client → Create client → Client authentication ON).
There are a few exceptions:

  1. OpenID scope – The openid scope isn’t included by default in all Keycloak versions. To avoid issues, add it manually: Client → [Gramps client] → Client scopes → Add scope → Name: openid → Set as default.

  2. Roles – Roles can be assigned either at the client level or globally per realm.

    • If you're using client roles, set the OIDC_ROLE_CLAIM config option to: resource_access.[gramps-client-name].roles
    • To make roles visible to Gramps, navigate to Client Scopes (the top‑level section, not under the specific client), then: Roles → Mappers → client roles → Add to userinfo → ON.

@DavidMStraub
Copy link
Member

Can you please implement the changes and rebase?

Thanks a lot!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants