Open qcaas-nhs-sjt opened 3 months ago
@konstjar - just tagging you here to see if you can provide some feedback on this issue? @qcaas-nhs-sjt has provided a lot of the details around his deployment using OpenID and I'm unsure what may be causing this behavior?
Linking to https://github.com/OHDSI/WebAPI/issues/1901
@qcaas-nhs-sjt Please check what redirect URL is defined in your Entra ID, does it include the port?
When we login to ATLAS, we are redirected to Entra ID and can login, once we are redirected back to the port that the server is run on rather than the proxy.
In our implementation of Atlas with WebAPI running on kubernetes, we are utilising Microsoft Entra ID to provide authentication. In our configuration, Atlas is configured as follows:
and our API Server is configured as follows:
https://sandbox-ohdsi.xlscsde.nhs.uk/atlas/#/home Our ingress configuration is as follows:
Atlas loads fine and can talk to the web api without incident, however when we login it redirects us in the wrong direction
Expected behavior
After login via oid we should be redirected to
https://sandbox-ohdsi.xlscsde.nhs.uk/WebAPI/user/oauth/callback
this should then redirect us to:
https://sandbox-ohdsi.xlscsde.nhs.uk/WebAPI/user/login/openid?redirectUrl=/home
Actual behavior
After login via oid we should be redirected to
https://sandbox-ohdsi.xlscsde.nhs.uk/WebAPI/user/oauth/callback
then redirect us to:
https://sandbox-ohdsi.xlscsde.nhs.uk:8080/WebAPI/user/login/openid?redirectUrl=/home
Steps to reproduce behavior