l6b1w (l6b1w) asked a question.
External Idp callback fails in Chrome browser. But it is working fine in Microsoft Edge browser
We use Okta for the SSO feature in our portal. We configured External Idp to Microsoft Azure AD. We used below npm package for the codebase.
It was working fine for the last year. But a couple of weeks before the okta callback is not working.
/api/v1/sessions/me API is failed after callback from Idp. It seems CORS is a related issue. It is not working in chrome and firefox.
It is working fine in Mircosoft Edge and "Chrome Incognito + enabled Block third-party cookies" browsers.
We are going to create a subdomain and configure it in Customization->Domain okta. Could anybody please guide us on this issue?
We used below npm package for the codebase.
@okta/okta-auth-js": "5.9.1
"@okta/okta-angular": "^3.2.2",
Hi @l6b1w (l6b1w),
Thank you for posting on the Okta community page!
I have done some research and managed to find the bellow documentation that might help with the CORS related issue:
If the above doesn't do the trick, I would recommend to try and capture a Fiddler trace while reproducing the behaviour to identify the root cause of the issue. Additionally, I would check the browser cookies for Chrome to make sure that no modifications were made.
I hope the above information is useful!
@flaviu.vrinceanu1.5628408972654734E12 (Customer Success Service Delivery) Thank you for your reply.
I have tested on Fiddler for this issue from chrome and chromium browsers. It is working fine with the chromium browser. But not working from the chrome browser.
I also set "allow all cookies" in my chrome setting. It seems the okta domain doesn't store cookies from the Idp on the chrome browser.
@flaviu.vrinceanu1.5628408972654734E12 (Customer Success Service Delivery) Could you please share your thoughts?