Signing in with Keycloak, Microsoft Entra ID and Google
Register the same Gadka redirect URI with any of these three providers. Each provider has its own issuer URL.
Choose your provider and add its settings to auth.oidc.providers in the OIDC configuration.
Register this redirect URI with the provider in each example.
https://gadka.example.com:6543/v1/auth/oidc/callbackKeycloak
- In your chosen realm, create an OpenID Connect client. Enable client authentication (confidential client) and the standard flow (Authorization Code).
- Add the redirect URI shown above.
- Copy the client secret to a file on the server.
- id: keycloak
tenant_slug: firma
display_name: Keycloak
issuer: https://sso.example.com/realms/firma
client_id: gadka
client_secret_file: /etc/gadka/oidc-client-secretMake sure users have verified email addresses in Keycloak.
Microsoft Entra ID
- Register an application with the Web platform and the redirect URI shown above.
- Create a client secret and save it to a file on the server.
- Use your directory's tenant ID in the
issuerURL.
- id: entra
tenant_slug: firma
display_name: Microsoft Entra ID
issuer: https://login.microsoftonline.com/<tenant-id>/v2.0
client_id: <id aplikacji>
client_secret_file: /etc/gadka/oidc-client-secretGadka requires both email and email_verified: true in the token. Check the app's token configuration to see whether Entra ID sends both. If someone with an existing account sees a message that they cannot access the workspace, a missing claim is the most common cause.
Google Workspace
- In Google Cloud Console, create an OAuth client ID and choose Web application as its type.
- Add the redirect URI shown above.
- id: google
tenant_slug: firma
display_name: Google
issuer: https://accounts.google.com
client_id: <id klienta>
client_secret_file: /etc/gadka/oidc-client-secret
auto_provision: true
allowed_email_domains: [example.com]Test SSO
Restart the server with sudo systemctl restart gadka. The login screen should show Sign in with … followed by the name from display_name. To check for provider connection errors, run journalctl -u gadka -n 50.