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
Using the admin-ui to manage a custom Identity Provider based on the default SAML 2.0 one
#40477
Hi everyone,
I am using Keycloak 26.x where I added a new custom SAML 2.0 provider that inherits from the base SAML 2.0 available in Keycloak to customize part of its behavior in dealing with SAML messages.
Now, I would like to add instances of this custom provider using the new React admin-ui (web console).
After adding the new provider jar file to the providers folder, I can choose the new provider type in the admin-ui but then the subsequent forms that are presented are different than those for the base SAML 2.0 Identity Provider.
Instead, I would like such forms to be exactly the same.
Peeking into the React code of the admin-ui (src/identity-providers/IdentityProviderCreate.tsx), I understand that the type of components used depend on the routes/paths. When a new Identity Provider is added, the URL path considered is /:realm/identity-providers/:providerId/add which is based on the provider ID, unique to each provider.
My custom provider has its own unique ID, different than that of the standard SAML 2.0 Identity Provider and so the admin-ui cannot re-use the same routes/components.
What is the expected/correct way to deal with this? Should I customize the admin-ui React code to add support for new provider IDs or is there a different way to go?
In case I should go through React code customization, how should I build it and inject in the Docker container where Keycloak is running, so that just the default admin-ui is overridden?
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.
Hi everyone,
I am using Keycloak 26.x where I added a new custom SAML 2.0 provider that inherits from the base SAML 2.0 available in Keycloak to customize part of its behavior in dealing with SAML messages.
Now, I would like to add instances of this custom provider using the new React admin-ui (web console).
After adding the new provider jar file to the providers folder, I can choose the new provider type in the admin-ui but then the subsequent forms that are presented are different than those for the base SAML 2.0 Identity Provider.
Instead, I would like such forms to be exactly the same.
Peeking into the React code of the admin-ui (src/identity-providers/IdentityProviderCreate.tsx), I understand that the type of components used depend on the routes/paths. When a new Identity Provider is added, the URL path considered is
/:realm/identity-providers/:providerId/addwhich is based on the provider ID, unique to each provider.My custom provider has its own unique ID, different than that of the standard SAML 2.0 Identity Provider and so the admin-ui cannot re-use the same routes/components.
What is the expected/correct way to deal with this? Should I customize the admin-ui React code to add support for new provider IDs or is there a different way to go?
In case I should go through React code customization, how should I build it and inject in the Docker container where Keycloak is running, so that just the default admin-ui is overridden?
Thanks in advance for any hint on this!
All reactions