User17056847738629796440 (Customer) asked a question.
Why is the sid cookie empty after SAML login?
I am trying to integrate my app with other SAML SSO apps. It appears that the others work by using an sid cookie that gets populated the first time logging in through okta. My app sends an ahtn request and gets a response after successful login. At this point, there is an sid cookie in the browser that is empty. I have two questions:
- How do I get this cookie to be non-empty? Am I missing a step? Do I need additional configuration?
- How do I use this cookie to authenticate a user? eg. Do I include this somewhere in the authn request? Is it a separate call to okta?
Hi @User17056847738629796440 (Customer) , Thank you for reaching out to the Okta Community!
This question is more appropriate for our dedicated Okta Developer Forum.
My advice would be to reach out via devforum.okta.com to take advantage of their expertise.
While we'll do our best to answer all of your questions here, this medium is more inclined towards Okta core products and features (non-developer work).
In the meantime, you can check the following integration guide to see if it helps with your use case:
https://developer.okta.com/docs/guides/build-sso-integration/saml2/main/
If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you.
Hope my answer helps!
--------------------------------
Ask the Experts: Okta Device Access Product Team Now Thru 3/22