Hi, I’m currently facing an issue with my ASP.NET core application. We are using Okta.AspNetCore (4.6.3)
Once a user has successfully authenticated with my application, using Okta SSO, they are unable to “duplicate” the tab they have ended up on.
This seems very similar to the issue put forward in this post
Something about how the Okta Callback path redirects back to the application after successfully authenticating does not interact with Edge’s (v141.0.3537.99 (Official build) (64-bit)) duplicate tab functionality.
In our application, we do not change the Callback Path from the default “/authorization-code/callback” and duplicating the tab leads to the new tab opening “https://{MYDOMAINHERE}/authorization-code/callback”, which ends up with an error from the MVC endpoint.
Once the page is refreshed, the user is still logged in and, duplicating the tab works as expected.