More than welcome @ssilvert!

Thanks for letting me know that.

Sure. I understand 👍

For the time being. I plan to use https://github.com/InseeFrLab/keycloakify. However, I wished if there was a native solution supported by KeyCloak.

React is good and will be enough for me. However, in my opinion, allowing multiple frameworks will help developers use their own design systems without needing to switch to another framework or re-implement some of their components.

Have a great day.

Best Regards.

Fadi

Hi @ssilvert,
I am the original author of https://keycloakify.dev.
Keycloakify is now quite mature it would be a shame this community effort was discarded.

If you are interested, instead of rebuilding the theming system from scratch, there are some very little changes
that Keycloak can do that would make Keycloakify's work much easier.
This approach would enable the community to easily come up with equivalent of Keycloakify for Vue, Angular, Svelte ect.
You would empower the community to build the tooling they need while you can focus on Keycloak's core features.

I am very interested in collaborating with you on that,

If you are interested please do not hesitate to reach out.

Best regards,

Hi @ssilvert,

I just wanted to let you know that I will soon release v6 of Keycloakify which features:

• A real type safe i18n customization API.
• Smaller bundle size, faster first print: Heavy use of React Suspence and dynamic imports in particular for only downloading the required locals.
• A better documentation.

You can check the v6 documentation website here: https://docs.keycloakify.dev/v/v6/how-to-use

I would be interested in knowing what are your future plans about customizability.
As I said, I'm very willing to keep maintaining and improving Keyclaokify for the foreseeable future. I think we can achieve great things with only minimal involvement on your side.

Best regards ,

Yes, we'll have to see what is a good fit for us. Ideally we'd like to use our existing stack of React and PatternFly for the sake of consistency. However, it might be that this stack is deemed to heavy for something like the login theme, in which case we'd have to consider alternatives.

My apologies for resurrecting quite an old thread. It's been 3 years and I am evaluating the login theme again in the latest version of Keycloak. It looks like the latest Keycloak updated the login theme but it is still a pure FTL implementation.

The rest of our application is written in React with our own design system and component library. Ideally we would like to use the out of the box solution from Keycloak (so no 3rd party library between us and Keycloak) and make it look and feel as close as possible to our own components as possible. I was hoping to get some clarification before we invest in redoing our login from scratch.

@ssilvert @jonkoops (sorry for the @ if you are no longer involved in the KC project) in the past 3 years has there been an update on the roadmap to migrate the KC login to use React and Patternfly like the other UI's in Keycloak?

Keycloakify now features a starter theme based on Shadcn/Tailwind: https://docs.keycloakify.dev/starter-themes/shadcn-ui-tailwind

For our use case Keycloakify is not an option sadly.

Ok, then you might want to take a look at what @kathari00 has been working on:

https://www.linkedin.com/feed/update/urn:li:activity:7431277873300226048/?originTrackingId=xS0%2BxF226hRX62vy4V7U%2FA%3D%3D

She’s a longtime Keycloakify contributor and has built a separate project (outside of Keycloakify) focused on creating simple themes using a WYSIWYG editor. It generates a theme bundle that’s closer to what you would expect if you had written the theme manually.

The idea is that it requires less long-term commitment to maintaining a third-party tool, while still enabling you to get something good enough, faster.

Out of curiosity, what’s the specific blocker preventing you from using Keycloakify?

It'll take more time to handle i18n and some utils, like usePrepareTemplate and getClassName, but in general I can confirm it works with vue

@AndreyYolkin This is so hype!
Don't hesitate to join our discord if you want to push this futher!

Hello, it's a pity Vue.js is not supported. Any change @AndreyYolkin could share is PoC ? I would love to try convert it and contribute here so Vue.js can be used with Keycloakify.

Hello @petitkriket,

Since we already support Svelte, I believe adding Vue support wouldn’t require too much additional effort.
The real challenge isn’t the initial implementation, but the ongoing maintenance.

I’m already close to the limit of what I can reasonably maintain while still making improvements elsewhere.

That said, there’s a major move to Login v2 currently in progress. Once that’s complete, we’ll be in a better position to reevaluate adding Vue support.

Totally get it. Keeping the surface of code to "manageable" is very important. Thank you for your feedback. If at some point you're up to it, i'd love to help, even with a simple QA + Test session.