By: ved singh user 26 Jun 2017 at 9:20 p.m. CDT

1 Response
ved singh gravatar
Hi, I'm able to successfully establish SSO exchange between Gluu IDP and single Service Provider. I also see that there are few cookies been created by Gluu IDP: shib_idp_session_ss, shib_idp_session,session_state,JSESSIONID I have two question here: 1) How does Gluu knows that user already has an existing logon session? I believe it is one of the above cookie. 2) Session info/session identifier transer to another SP. Here the scenario is : The website(say Site-A) with which I've been able to establish SSO exchange with Gluu, has a link which takes user to second Service Provider(Say Site-B). Site-B, also needs to authenticate user against the same Gluu IDP instance.Inorder to provide SSO experince,the user should not be asked to login again at Site-B. My doubt is what data - session info/session identifier, do I need to transfer(perhaps as a query param) from first service provider (Site-A) to the second service provider(Site-B), so that Gluu knows that user has already been logged on (and there by user does not have to login again) and it returns the SAML reponse to Site-B as per its metadata. Thanks.

By Mohib Zico staff 27 Jun 2017 at 1:31 a.m. CDT

Mohib Zico gravatar
Hi Ved, >> My doubt is what data - session info/session identifier, do I need to transfer(perhaps as a query param) from first service provider (Site-A) to the second service provider(Site-B), so that Gluu knows that user has already been logged on (and there by user does not have to login again) and it returns the SAML reponse to Site-B as per its metadata. No, you don't need to transfer anything by yourself if you are using same browser ( different tab ) for various SPs. 2nd, 3rd, 4th login will happen automatically without asking for credential.