Skip to content
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

JHipster Angular with Keycloak: Missing keycloak-angular and keycloak-js in Frontend Generation #28626

Open
YassineOularbi opened this issue Feb 6, 2025 · 4 comments

Comments

@YassineOularbi
Copy link

Why doesn't the JHipster generator generate Angular with keycloak-angular and keycloak-js when Keycloak is the identity provider, and is there any tutorial or documentation on how to integrate them?

@mraible
Copy link
Contributor

mraible commented Feb 6, 2025

We made a design decision years ago to do all OAuth authentication on the backend with Spring Boot. This is more secure, doesn't require us to use different OIDC libraries for front-end frameworks, and works with most OAuth providers. We don't want to force our users to use Keycloak, especially in production.

@atomfrede
Copy link
Member

When you select oauth2 during generation it will create a keycloak config and docker file.

@YassineOularbi
Copy link
Author

Without using those libraries, some issues arise. For example, when signing out from the JHipster interface in the Gateway, the backend session is destroyed, but the session in Keycloak remains active. Similarly, in JHipster Registry, logging out triggers the event listener in the Keycloak interface, resulting in a "Logout ERROR."

@YassineOularbi
Copy link
Author

If we can't track login and logout events from Keycloak, we can still save user sessions and track their activities using alternative approaches.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants