<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z0000A4pNZECQ2Okta Classic EngineAuthenticationAnswered2024-06-17T07:08:20.000Z2024-05-13T21:11:34.000Z2024-05-31T17:02:52.000Z

70jij (70jij) asked a question.

Express sample app works in dev but not in org Okta tenant

Hello,

 

I successfully deployed the sample Express.js app from the Okta quickstart, using a test developer Okta account. I run the app on a container on localhost, and everything works fine and as expected.

 

However, when I deploy this to AWS ECS behind an ALB, it doesn't work, even though the code being deployed is identical. One of two things happen when trying to hit the Okta protected route:

 

  1. The request times out, and a 504 Gateway timeout is thrown by the AWS ALB.
  2. I get a 403 error from the application.

 

In the application logs, though, I can see that the application has received the callback code and state from Okta.

 

Does anyone have any clues as to where the issue might be? Is the likely culprit the App Integration and/or security policies in the org Okta tenant?


Loading
Express sample app works in dev but not in org Okta tenant