{
“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”
}
I’m not sure I understand where this error message is coming from. Are you using one of Okta’s SDKs for this?
i’m trying to Integrate okta with LDAP server as the ID service for my application
The redirect to okta screen when im clicking on my application signin button is happening but when i’m entering the credentials its redirected with errorCode=User_Authentication_Failed
This was working last year when i tested , but not working now
The error message is from my applications log where the Token is not getting set in cookies now
the JWT is supposed to be created from my application after validating the SAML response
Does it have anything to do with “third-party cookie deprecation” is my main query ?
“If an application hosted on your domain (mycompanyapp.com) redirects to your Okta subdomain (mycompany.okta.com) for login and then returns users to your own domain, third-party cookie restrictions will limit how your app can introspect or extend the Okta session “ - from okta docs
So is this a custom OIDC application that requests and receives tokens from Okta? Or is this for our LDAP Interface?
It is a custom OIDC application , but just that it uses delegated authentication
delegated authentication if you want LDAP to authenticate your users when they sign in to Okta.
Okay, got it. So when your application requests tokens from Okta, is it able to actually receive them from the /token endpoint?
How does your application then manage storing the tokens within a cookie? Do you happen to use any Okta SDK or open-source framework to handle the OIDC integration and session management/token storage?
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.