Troubleshooting OAuth/Okta/DataHub Integration "502 Gateway" Issue

Original Slack Thread

hi all. this might be a dumb question, but we are having an “issue” with our oauth/okta/datahub integration.
so far what we see is that after a successful login, we get a PLAY_SESSION cookie with a JWT token that expires in 24 hours(this is the default).
the behavior we are seeing is that after expiration, if an attempt is made to navigate back to datahub, then we are met with a 502 Gateway page and not attempt is made to ask for a refresh or reauth of the token.

if we clear the token(either all tokens or that one specifically) then we are forced to reauth, which is expected.

i am the worst at oauth stuff, so I’m curious if this is a datahub thing or an okta thing? or both?
any help would be greatly appreciated.

Hey there! :wave: Make sure your message includes the following information if relevant, so we can help more effectively!

  1. Which DataHub version are you using? (e.g. 0.12.0)
  2. Please post any relevant error logs on the thread!

Datahub version: v0.11.0
On k8s using helm for deployment