New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow existing mappers for Custom Identity Providers #21154
Comments
@danielFesenmeyer It would be ideal:
Currently Keycloak is optimized for (1), but doesn't allow (2). How to improve that?I am thinking about something like this method on IdentityPRovider:
And update accordingly I think this approach will allow both (1) and (2) if I don't miss anything? Contribution welcome :-) |
@mposolda I think it will work that way. I'll provide a PR. |
- Also allows to use existing mappers for custom Identity Providers without having to change those mappers Closes keycloak#21154
- Also allows to use existing mappers for custom Identity Providers without having to change those mappers Closes keycloak#21154
- Also allows to use existing mappers for custom Identity Providers without having to change those mappers Closes keycloak#21154
- Also allows to use existing mappers for custom Identity Providers without having to change those mappers Closes keycloak#21154
- Also allows to use existing mappers for custom Identity Providers without having to change those mappers Closes keycloak#21154
- Also allows to use existing mappers for custom Identity Providers without having to change those mappers Closes keycloak#21154
- Also allows to use existing mappers for custom Identity Providers without having to change those mappers Closes keycloak#21154
- Also allows to use existing mappers for custom Identity Providers without having to change those mappers Closes #21154
- Also allows to use existing mappers for custom Identity Providers without having to change those mappers Closes keycloak#21154
- Also allows to use existing mappers for custom Identity Providers without having to change those mappers Closes keycloak#21154 Signed-off-by: Kamontat Chantrachirathumrong <14089557+kamontat@users.noreply.github.com>
Description
Currently, for each IDP Mapper, the list of supported mappers is defined by the method IdentityProviderMapper#getCompatibleProviders():
For example, for
UserAttributeMapper
, the compatible providers are the Keycloak OIDC Provider and the standard OIDC Provider.https://github.com/keycloak/keycloak/blob/41e253c054d7db1682a0865603bdf20d0893ba6f/services/src/main/java/org/keycloak/broker/oidc/mappers/UserAttributeMapper.java#LL48C1-L48C1
We have implemented our own Azure OIDC Provider, based on the standard OIDC Provider, and our customers would like to use (probably) all of the mappers which are compatible to the standard OIDC Provider.
Currently this is not easily possible. One of those mappers is
UserAttributeMapper
.Discussion
No response
Motivation
We have built a kind of patch, which supports all mappers for our custom provider, which are supported by the standard provider.
It would be helpful if we could do this without patching Keycloak.
Details
No response
The text was updated successfully, but these errors were encountered: