Repository navigation
Replies: 1 comment
|
|
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hello contributors,
I’m new to Keycloak and I find it to be a really powerful and active open-source IAM project.
I’m planning to use Keycloak 26.3.2 as an SSO system, integrating both my mobile app and web client via OIDC. However, I’ve run into a question during development:
I noticed that many HTTP responses from Keycloak return with a Media-Type of document. This causes the whole page to reload whenever a user clicks a button, which results in a flickering UI and not-so-great user experience. From what I can tell, the project isn’t designed as a front-end/back-end separated architecture.
So my question is: what’s the reasoning behind this design? And what would be the recommended approach if I want to build a purely front-end client that communicates with Keycloak via JSON, instead of overriding login.ftl with Freemarker templates — especially since my frontend teammates are not familiar with Freemarker.
Maybe this question has already been asked many times before—please don’t take it as impatience. If you could just point me to any relevant discussions or documentation, that would be greatly appreciated.
Thanks a lot! 🙏
All reactions