:information_source: If you have a question, please post it on the Okta Developer Forum instead. Issues in this repository are reserved for bug reports and feature requests.
I'm submitting a
[x] bug report
[ ] feature request
Background info
With 'router' feature flag enabled, the user is not able to navigate back after being redirected to the Okta-hosted widget login page unless they login.
Redirecting to the Okta-hosted widget login page adds the following pages to session history:
The call to /authorize endpoint
The call to /signin/refresh-auth-state endpoint
The call to / endpoint (current page)
If the user clicks the browser's 'back' button, they will still be on the login screen, instead of going back to the page that redirects them to the login page.
The back button behaviour can be observed in Safari and Firefox, but not in Chrome/Edge. 'Back' button in Chrome-based browsers somehow manages to navigate back correctly.
Expected behavior
After redirect to the Okta-hosted login page, the user should be able to navigate back if they do not wish to proceed.
What went wrong?
After redirect to the Okta-hosted login page, the user is unable to navigate back if they do not wish to proceed.
:information_source: If you have a question, please post it on the Okta Developer Forum instead. Issues in this repository are reserved for bug reports and feature requests.
I'm submitting a
Background info
With 'router' feature flag enabled, the user is not able to navigate back after being redirected to the Okta-hosted widget login page unless they login.
Redirecting to the Okta-hosted widget login page adds the following pages to session history:
If the user clicks the browser's 'back' button, they will still be on the login screen, instead of going back to the page that redirects them to the login page.
The back button behaviour can be observed in Safari and Firefox, but not in Chrome/Edge. 'Back' button in Chrome-based browsers somehow manages to navigate back correctly.
Expected behavior
After redirect to the Okta-hosted login page, the user should be able to navigate back if they do not wish to proceed.
What went wrong?
After redirect to the Okta-hosted login page, the user is unable to navigate back if they do not wish to proceed.
Steps to reproduce
This can be reproduced with the React Sample Application for Okta (Okta-hosted login) at https://github.com/okta/samples-js-react
Your environment