Replies: 3 comments
-
|
Hi @edewit, sorry for the direct ping. I’ve been following your work on Keycloak UI customization and would really value your input on this discussion if you have a moment. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
I don't know of any documentation that has been removed, but there is documentation here. So extending the admin ui with the npm packages is supported, but I guess it's more geared towards using parts of the UI in your own application not so much extending it for a quick example look at this keycloak/keycloak-quickstarts#679 So for your use case, adding one screen to realm settings, it might be easier to use the Java based extension That the routes aren't exported is on purpose, like I mentioned before it was meant to be something that you would use in your own application not so much as a way to extend the UI. But if you do want to use react to extend then I would suggest not using the npm package, but instead adding your changes on top of the frontend. I don't know of any essential react hooks that are not exported, or why it would be unclear to pass i18n I would suggest to either use the create-keycloak-theme tool or having a look at the quickstart |
Beta Was this translation helpful? Give feedback.
-
|
The documentation made it seem like you could create your own admin console custom version. The issue with the java based extension is that it only saves to some special generic location. It does not integrate with nor can access existing context. I can't add or modify existing sources (like realm config or identity provider config - where scope is required). Like building a custom extension java package - i would also like for it to be configurable through admin UI. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
We are working on extending the Keycloak Admin Console to support a feature. We need to add a tab to the realm settings. However, we face challenges to even make simple changes to the console.
Background
We are adding a dynamic realm branding feature. This feature allows realm admins to configure branding (logos, favicons, color palettes) without deploying new themes or restarting the server.
What we've built so far:
What we're trying to do:
Add a new tab to the Realm Settings section of the Admin Console to expose this feature through the UI. The tab would follow the same layout and UX conventions as the existing Quick Themes tab, but communicate with the Admin API instead.
Challenges
1. Lack of Documentation for React-based Themes
2. Issues with
@keycloak/keycloak-admin-uiModule (v26.4.5)3. Issues with
@keycloak/keycloak-ui-sharedModuleQuestions
Any guidance or suggestions would be greatly appreciated. In addition, I'd be happy to contribute back to the project by fixing issues and writing docs if needed.
Beta Was this translation helpful? Give feedback.
All reactions