
RajeshD.00986 (Customer) asked a question.
Hi,
Just want to know about the third party cookies disablement in okta.
we have OIDC applications which use okta as authentication.
I would like to know the best way to resolve without any code changes on ui side .
Also if we change the domain name , we have many applications integrated with okta which might require to the embed link on app side/sso url/entity ids ?
I gone through the okta help articles but not sure which approach to follow and let us know your views like how you are handling ?

Hi @RajeshD.00986 (Customer) , Thank you for reaching out to the Okta Community!
If you haven't already please review Deprecation of 3rd Party Cookies in Google Chrome as it contains information about testing the impact and advice on How to Prepare Your Self-Hosted Okta Sign-in Widget to Work without Third-Party Cookies if you use the widget for your implementation.
Our recent blog, also mentions the following:
Third-party cookie deprecation affects web applications that rely on the Okta session for user context
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.
In addition to that, I recommend reaching out to our dedicated Developer forum via devforum.okta.com to take advantage of their expertise.
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!
--
Help others in the community by liking or hitting Select as Best if this response helped you.