Repository navigation
About SSO with 2 Different Clients in The Same Realm #14239
Unanswered
korkutkose
asked this question in
Q&A
Replies: 0 comments
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.
Hi there,
So we are using keycloak 19.0.1-legacy in our production environment. Recently we got a request about a possible SSO solution via Keycloak. Before this, we were using keycloak with an OIDC client in our project which is powered by Springboot.
However the external product they would like to use cannot use OIDC protocol and only supports SAML. Hence, we have created another client in the same realm for this product.
If we would like to login the product, product redirects us to the keycloak login screen and we can successfully login without any issues or whatsoever.
However, when we login to the our main product and got a session, external product cannot validate this session (it's embedded in one of our main product's screen, kind of iframe).
It's like they cannot exchange sessions between each other. If i externally post the credentials to the external product, again I can get a session and use the product within iframe.
Maybe it's worth to mention that, 2 products are running in completely different domains. I am suspecting it's failing because of this.
Is there a guide or something I can follow for a possible configuration mistake? Or should we implement a custom solution for this?
Cheers.
All reactions