User16660261464889678833 (Customer) asked a question.
We are currently facing an issue with our servlet application that is integrated and secured by Okta SAML using Picketlink.
The scenario is as follows: After successfully logging into the application, the application works as expected. However, upon logging out and subsequently attempting to log in again, we observe that a JESSION ID is being appended to the sign-on URL resulting in a 404.
It's worth noting that we have deployed identical code across four environments - Test, Stage, Preprod, and Prod. However, this particular issue only occurs in the Preprod and Prod environments. Additionally, there is a difference in Okta versions, with Test and Stage utilizing Okta preview, while Preprod and Prod employ the Okta production version.
We would greatly appreciate any insights or guidance on the potential reasons behind this behaviour, as the uniformity of the codebase across environments leaves us confused regarding the root cause.
Hi, @User16660261464889678833 (Customer)
Thank you for posting on our Community page!
Here is a helpful article and video to troubleshoot the 404 error:
https://support.okta.com/help/s/article/Receiving-404-error-when-attempting-to-sign-into-application?language=en_US
Should you still have issues after checking the steps in the article, I recommend opening a case with support to take a closer look.
Thank you for reaching out to our Community and have a great day!
_____________________________________________________________________________
What you missed: new product releases and other announcements
_____________________________________________________________________________
Community members help others by clicking Like or Select as Best on responses. Try it today.
_____________________________________________________________________________