Is this expected behavior? We use a spa and built our own login form and using okta-auth-js APIs to authenticate. So, user visits the /login page (SPA initial page load occurs). User authenticates using signInWithRedirect, gets redirected to the authorize endpoint, then redirected back to /implicit/callback URL. This causes the SPA to fully reload again. Am I missing something? I wouldn’t expect the SPA to have to reload. It makes sense in theory but not sure if we misconfigured something.
Can you try using signInWithCredentials instead? That should prevent there from being a redirect to Okta to handle the primary authentication, allowing the full login process to be completed within your application directly.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.