<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z00007dDIK7CAOOkta Classic EngineSingle Sign-OnAnswered2022-05-06T23:02:02.000Z2022-05-06T16:26:26.000Z2022-05-06T23:02:02.000Z

JeremyO.17379 (Customer) asked a question.

User in organization sent directly to Okta app rather than redirected to appropriate Hub

My organization uses Okta with Munis. Munis is a SaaS application my organization uses. We upgraded our Munis version and with that upgrade came SSO. We have two Okta agents on each of our domain controllers to sync between active directory and Munis so that people have SSO. 99% of us are fine, except for 1 user. For 99% of users, we sign into with Okta and are automatically redirected to our Munis landing page. For this 1 user, he is signed directly into the Okta app. What happens after signing in is the browser immediately directs here

 

https://xxxx.okta.com/app/UserHome and a second after, redirects to https://xxxxt.okta.com/enduser/callback

 

He has to open the same shortcut/bookmark/url a SECOND time, in the same browser session, to reach his Munis landing page.

 

I should note this only happens on his computer. He can sign in fine on my computer.

 

From my testing, I know this is a chromium specific issue. This only happens in chromium browsers like Edge & Chrome. This does not happen in Firefox and Internet Explorer, which run on different web engines. Because this is affecting ALL chromium browsers, there is no specific browser setting or cookies to try and experiment with. Changing something in Chrome (our default browser in the org) is not going to affect Edge, which is also experiencing this problem.

 

I have contacted support and they are just as perplexed as me. Even support doesn't know what is going on. They spent over an hour on this user's computer yesterday with no resolution. Can anyone help? Thank you!!


This question is closed.
Loading
User in organization sent directly to Okta app rather than redirected to appropriate Hub