Redirect not working after login - Okta Developer Community 👋 I’m building an app in JS TS that supports SSO, and I’m having trouble getting Okta to redirect back to my app after logging in There are 2 scenarios: When I’m already logged into Okta, Okta will redirect correctly back to my app When I’m not logged into Okta, Okta will redirect to their login page, but once I login, it just goes to the Okta dashboard and not to my app I’m new
403 access Forbidden. Loggin isssue - Okta Developer Community Hi technical team I am learning about okta with login module, I have problem when registering account with developer role But I have encountered some problems reported as: “Access Forbidden You don’t have permission to…
Login infinite loop after MFA configuration - Questions - Okta . . . After trying to disable MFA for my developer account (which uses Google to login), I’m stuck in an infinite loop Here are the steps: Go to the login page for developer accounts Click on “Continue with Google” Let the infinite cycle begin! Looking at the network requests, I can see that the looping starts after a request to Google is made (so I’d believe I effectively logged into Okta
How to Bypass Okta Sign-in Page in External IdP-initiated Login Flow 3- User gets redirected to Okta to enter their username in Okta Login Page 4 - User enter their username (External IdP username) in Okta Login page 5 - User get logged in to the OIDC app Is there a way to bypass 3 4? (We’re aware that we can use the routing rules for IPs) Please let us know if there are any methods to achieve this
How to pass login_hint into authorization url - OAuth OIDC - Okta . . . Hi, I am quite new in OKTA I want to pass login_hint in OKTA sign on page so that the username get filled with login_hint I want to know that inside OKTA portal where we can define the parameters which are part of URL i e where i need to define the login_hint Can some one please help Thanks in advance
Account owner unable to login - permission denied - Questions - Okta . . . Since our Okta users can still login to our Web apps using the (Okta auth) (thanks to internet god) I’m taking this precious time to take a decision with concerned businesses as to Drop OKTA for now (cheap solution) or create and configure a new account (wich is gonna be costy and a pain)
Redirect URI Defaulting to HTTP Instead of HTTPS in ASP. NET Core with . . . I’m currently integrating Okta OpenID Connect (OIDC) authentication in an ASP NET Core application I’ve configured the Okta app settings and provided the necessary redirect URIs, but I’m running into an issue where the redirect_uri in the authentication request defaults to HTTP instead of HTTPS
We are experiencing a persistent looping behavior in the login process We are encountering a login looping issue during the authentication process integrated with Okta The problem is browser-specific: while Firefox works without issues, Chrome consistently experiences a redirect loop, and Edge shows intermittent behavior