Purpose
This article explains how external identity providers can be connected to Keycloak so users can authenticate through an external IdP instead of only local Keycloak-managed credentials.
Overview
Keycloak supports identity brokering, which means it can delegate authentication to external identity providers. Officially, Keycloak supports brokering with external OpenID Connect and SAML 2.0 identity providers, and this is configured through the admin console.
This allows the platform to integrate with enterprise identity systems or social login providers while keeping Keycloak as the centralized access point for applications.
What identity brokering means
In this model, Keycloak remains the identity layer seen by the platform, but it relies on an external provider to authenticate the user.
The practical flow is:
- a user starts login through Keycloak
- Keycloak redirects the user to the external IdP
- the external IdP authenticates the user
- Keycloak receives the identity result and completes the login
- the platform receives a Keycloak-issued token
Keycloak documents this model as identity brokering and notes that external OIDC and SAML providers can be configured in the admin console.
Where to configure it
To connect an external identity provider:
- open the Keycloak admin console
- select the
giottorealm - go to the Identity Providers section
- add and configure the external provider
- save the configuration
- test the login flow
This is standard Keycloak administration.
Supported provider types
The standard setup described in the official Keycloak docs covers:
- OpenID Connect identity providers
- SAML 2.0 identity providers
- common social login providers configured through the admin console
Keycloak also documents identity brokering and account linking behavior around external providers.
What to configure
The exact fields depend on the provider type, but in general you will configure:
- provider type
- client or application identifiers
- client secret or equivalent credentials when needed
- issuer / metadata / discovery information
- redirect or callback settings
- optional attribute or identity mappers
Once configured, the external provider becomes part of the realm’s login options.
How this affects users
When identity brokering is enabled, Keycloak can authenticate users through the external provider and then map or create corresponding users in Keycloak storage, depending on the configured flow. Keycloak’s administration guide describes this under identity brokering and first-login behavior.
This means external authentication can still fit cleanly into the platform’s user and role model.
How this connects to the platform
From the platform perspective, the main benefit is that authentication can remain centralized in Keycloak while user credentials are managed externally.
That allows:
- enterprise SSO integration
- federation with external identity providers
- a smoother user experience in organizations that already have an identity system
Best practices
Start with one provider
Configure and validate one external provider first before adding multiple providers.
Test in the correct realm
Make sure the provider is configured in the intended realm, in your case giotto.
Review user and role mapping behavior
Authentication can succeed, but access still depends on how users and roles are represented after login.
Keep the provider config documented
Since external IdP setup often involves coordination with another team, it is useful to document the configuration choices and any mapper behavior.
Suggested external references
- Keycloak Server Administration Guide
- Keycloak identity brokering documentation
- Keycloak securing applications docs
Comments
0 comments
Article is closed for comments.