JeanM.80687 (Customer) asked a question.
We are currently facing an issue where, during the authorization workflow in our Okta Classic Engine environment, a page refresh causes a loss of context for the authorize request. This differs from the behavior in our Okta Identity Engine environment, where the context is maintained even after a refresh.
Here are the specific behaviors we have noted:
Okta Classic Engine
A brief display of the full URL with query parameters before redirecting to https://our-domain.com.
Loss of application context upon page refresh, redirecting users to the Okta dashboard instead.
Okta Identity Engine
Retains the full URL with query parameters even after a page refresh, maintaining the application context.
We would like to know if there is a way to retain the full URL with the application ID in the Okta Classic Engine environment, maintaining the application context even after a page refresh, akin to the behavior in the Identity Engine environment, but without upgrading.
We tried with older Sign-In widget versions and it looks like this change was introduced in version 2.3. Before that the full URL was displayed
Hi Jean Morales,
Thank you for raising this case with Okta. My name is Cristian from the Support Team.
I have checked internally, however I did not find a mention that there is a change in logic or code between Classic and Identity Engine.
Since you are mentioning that the application context is lost on refreshing the page, I suspect that this is a particular issue that you are encountering, maybe due to browser or Okta.
I strongly recommend you open a support case directly with our team, so we can get more information about the environment and see the flow exactly in order to further troubleshoot.
Thank you for your understanding!
Best regards,
Cristian Lazar
Okta Global Customer Care
Thanks Christian, I've created a support case for this issue