You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Combine User federation with OpenID Identity provider
#36220
We want to use Keycloak as an identity provider for a few of our development tools.
As we want to be able to use local accounts as well as accounts from our Azure tenant.
Keycloak is configured to authenticate the users through Microsoft Azure AD and this is working fine.
The drawback we have is that user are only available in Keycloak after they have logged in at least once.
So the idea was to create a custom user storage provider for user federation that can synchronize the users directly from Azure.
But for this to work the users created through the storage provider must be linked to the identity provider.
This requires the email and ID.
But the ID is the value "sub" from the JWT when the user authenticates.
Therefore, it seems not possible to perform the linking beforehand.
Am I missing some information or would this even be the right approach?
Looking forward to some input.
Thank you very much.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
We want to use Keycloak as an identity provider for a few of our development tools.
As we want to be able to use local accounts as well as accounts from our Azure tenant.
Keycloak is configured to authenticate the users through Microsoft Azure AD and this is working fine.
The drawback we have is that user are only available in Keycloak after they have logged in at least once.
So the idea was to create a custom user storage provider for user federation that can synchronize the users directly from Azure.
But for this to work the users created through the storage provider must be linked to the identity provider.
This requires the email and ID.
But the ID is the value "sub" from the JWT when the user authenticates.
Therefore, it seems not possible to perform the linking beforehand.
Am I missing some information or would this even be the right approach?
Looking forward to some input.
Thank you very much.
All reactions