I would suggest reconsidering this approach and rather leverage what is
already there. Using the login pages from Keycloak is the best practice, in
terms of security, flexiblity and maintenance. Using our connect adapter
(or a different OIDC library) is also highly recommended over trying to
implement your own.
On Tue, 23 Oct 2018 at 14:57, Shubham Akodiya <sakodiya(a)grepruby.com> wrote:
Hi Team,
I'm integrating the node application with keycloak without using
*keycloak-connect
library, *So In this case, I'm handling the following things at my end -
- Managing user session.
- Display our app login page instead of keycloak default page.
- Performing the user authentication and authorization using the keycloak
URLs.
I have taken the reference of this app
<
https://github.com/v-ladynev/keycloak-nodejs-example> but I'm facing the
problem in SSO and I'm guessing that this is happening because of not using
the keycloak library, In which session is managed by keycloak. So how to
achieve this in my application ?
Thanks,
Shubham Akodiya
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user