<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D5KZ00001WYwaB0ATOkta Classic EngineAuthenticationAnswered2025-11-05T14:26:54.000Z2025-10-29T17:15:18.000Z2025-11-05T14:26:54.000Z

ArunrajA.02187 (Customer) asked a question.

JWT Token not getting set in chrome when validating with Okta

{

 "cookieId": "SAML_JWT_TOKEN",

 "error": "http: named cookie not present",

 "file": "/auth/src/saml/auth.go:78",

 "func": "src/saml.TokenValidity",

 "level": "error",

 "module": "default",

 "msg": "Error while fetching the JWT token from cookie",

 "time": "2025-10-28T13:43:22Z"

}


  • User17157611498146715886 (Customer Support Online Community and Social Care)

    Hello @ArunrajA.02187 (Customer)​ , thank you for contacting Okta Community!

     

    I've reviewed our documentation for something relevant. It looks like your question is more appropriate for our dedicated Okta Developer Forum. I advise reaching out via devforum.okta.com  as they will have more insight into this topic. 

    In the meantime, you can reference this article from Okta Developer as a possible starting point: 

    Work with Okta session cookies

     

    While we'll do our best to answer your questions here, this medium is more inclined towards Okta's core products and features (non-developer work).

     

    Regards. 

    --

    Help others in the community by liking or hitting Select as Best if this response helped you.

    Expand Post
  • BrandonB.06003 (Customer)

    Could be a cookie issue. some browsers reject the okta cookie especially if youre trying to read the cookie from a different domain (look into samesite cookie topic)

This question is closed.
Loading
JWT Token not getting set in chrome when validating with Okta