uqnts (uqnts) asked a question.
302 Found ERROR in PeopleSoft implementation with OAC
We recently completed the integration between Okta and PeopleSoft using the Okta Access Gateway.
The implementation works correctly with Internet Explorer; however, it does not work with Google Chrome and Mozilla.
When the user clicks on the Okta dashboard button, the authentication process starts, and they are redirected to the PeopleSoft URL. However, before displaying the application, the user is redirected back to the Okta dashboard. Upon inspecting the .har files, we see that in the URL of the authentication GET request, we receive a code 302 Moved Temporary / 302 Found.
Any idea on what we could investigate or why it only works with Internet Explorer?
Hi Gilberto, thank you for posting!
One common cause of a 302 error redirecting back to Okta after authenticating into OAG application could be if you have a HA cluster of multiple OAG nodes, and the front-end network is not properly enforcing sticky sessions. Each OAG worker node operates independently and expects all requests for a particular session to remain localized to that node. So if a session is initiated on one node, but then subsequent request suddenly gets directed to another node, it would be expected for that second node to redirect back to Okta to initiate a new session. You can find more details on load balancer/sticky session requirements for OAG at following link: https://help.okta.com/oag/en-us/content/topics/access-gateway/about-load-balancers.htm
Although this would not necessarily explain different behavior between different browsers. There are no known issues with Chrome/Firefox with OAG so it is difficult to speculate on why you may be seeing this behavior. We would suggest checking your browser security settings further for anything that may be influencing the behavior.