
MaxH.79374 (Customer) asked a question.
Attempting to access the following:
My Settings (/enduser/settings)
Okta End-User dashboard (/app/UserHome)
Results in a new request to verify using Okta Verify. After I do this, I am redirected back to /admin/home. Attempting to navigate again will skip the verify request, but I am still redirected back to /admin/home. After a short period of time (probably less than a minute) attempting to navigate again results in a new request to verify using Okta Verify.
After some experimentation, I found navigating to "My end user dashboard" from the admin page (/app/UserHome?fromAdmin=true) does work.
What is happening here?

Hello @MaxH.79374 (Customer) Thank you for posting on our Community page!
You have discovered a classic quirk of Okta's routing engine! What you are experiencing is a collision between Admin Session Policies and Default Administrator Routing.
Because your account has administrative privileges, Okta treats your session much differently than a standard end-user session. Here is exactly what is happening behind the scenes:
1. The Constant Okta Verify Prompts (Admin Policy)
Even though you are trying to access the End-User Dashboard, Okta recognizes your account as an Administrator. Admins are governed by the Okta Admin Console sign-on policy, which is typically configured to be highly restrictive. It often requires step-up MFA (Okta Verify) and has very aggressive idle timeouts (often set to just a few minutes, which explains why you get prompted again so quickly).
2. The Redirect to/admin/home (Lost Context). When you hit /enduser/settings or /app/UserHome directly, Okta pauses your request to enforce that strict Admin policy and prompts you for Okta Verify.
However, once you successfully authenticate, Okta's default routing behavior for administrators kicks in. Okta assumes an Admin completing an MFA challenge wants to do administrative work, so it drops your original destination (/enduser/settings) and forcefully routes you to /admin/home.
If you try the URL again immediately, you don't get the MFA prompt (because your admin session is active for that brief window), but Okta’s routing engine still sees an Admin navigating to a root-level app and redirects you back to the Admin Console.
3. Why ?fromAdmin=true Works
The ?fromAdmin=true query parameter is an explicit override built into Okta.
When you click "My end user dashboard" from the Admin UI, Okta appends this parameter to the URL. It explicitly tells the Okta routing engine: "This user is already an Admin, but they are intentionally stepping down into the End-User context. Suspend the automatic Admin Console redirect."
How to manage this:
Thank you for reaching out to our Community and have a great day!
--
Help others in the community by liking or hitting Select as Best if this response helped you.