Keycloak
Waldur supports integration with Keycloak identity manager.
Below is a guide to configure Keycloak OpenID Connect client and Waldur intergration.
Configuring Keycloak
Instructions below are aimed to provide a basic configuration of Keycloak, please refer to Keycloak documentation for full details.
- Login to admin interface of Keycloak.
- Create a new realm (or use existing)

- Open a menu with a list of clients.

- Add a new client for Waldur by clicking on
Create clientbutton.
- Make sure that
Client authenticationis enabled.
- Change client's Valid redirect URIs to "*".

- Copy secret code from
Credentialstab.
- You can find the settings required for configuration of Waldur under the following path on your Keycloak deployment (change
test-waldurto the realm that you are using):/realms/test-waldur/.well-known/openid-configuration
Configuring Waldur
Keycloak is configured in the user interface, not in settings.py.
-
Open Administration → Configuration → Identity providers.
-
Open the Keycloak provider details through the
Editentry of its dropdown menu. -
Fill in
Client ID,Client secretandDiscovery URLfrom the steps above. For extra security, enable SSL, PKCE and post-logout redirect. - Map user attributes in the
… fieldinputs. Each takes a space-separated list of claims, and the first claim the user has is used, for exampleschac_home_organization affiliation org. Claims are read from the UserInfo response and the validated ID token, with UserInfo taking precedence.User claimandExtra fieldsread UserInfo only. The Re-discover entry in the same menu (Discovery wizard before the provider is configured) suggests a mapping from the provider's published claims.
The Keycloak card is Waldur's generic OIDC provider, so other OpenID Connect providers are set up the same way. See Microsoft Entra ID for a worked example.

