Session ID issue due to cross domain

Hello,

Our application moving from A.com to B.com domain. Okta issuer is in A.com domain. Now I am facing issue getting session ID from sessions/me API. Is there any alternate way to get the session ID from client side. It is an angular application.

Any help will be appreciated. Thank you!

You’re likely running into 3rd party cookie issues, since the sessions/me call is dependent on being able to reach the Okta domain to get to the Okta session cookie set there. The only way to avoid this issue is to either host your app and your Okta org on the same domain (which you seem to be migrating off of) or stop using CORS requests like this and handle everything via redirect