Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OpenID Connect HTTP Callback Url #4507

Closed
knom opened this issue Jan 26, 2024 · 3 comments
Closed

OpenID Connect HTTP Callback Url #4507

knom opened this issue Jan 26, 2024 · 3 comments
Labels

Comments

@knom
Copy link

knom commented Jan 26, 2024

We have CORAL running on an HTTPS instance of Fargate in AWS.

Expected behavior:
Using Docker installation guide at https://docs.coralproject.net/, Redirect URI in OpenID Conenct login is having http instead of https i.e.

http://talk.sitename.com/api/auth/oidc/callback instead of https://talk.sitename.com/api/auth/google/callback

Actual behavior:
OpenID Connect redirect URI should include https instead of http
The Config URL Textbox shows the hardcoded http://... value - and it cannot be changed.

Related Issues:
Similar to #3667 - but for OpenID Connect.

Versions:
Using latest version of Docker installation

@knom knom added the bug label Jan 26, 2024
@losowsky
Copy link
Member

losowsky commented Feb 5, 2024

Thanks - well take a look.

@nick-funk
Copy link
Contributor

We do not support serverless hosting or network stacks with Coral.
Our system reconstructs secure and insecure url's when it finds tenants and other requests here:
https://github.com/coralproject/talk/blob/develop/server/src/core/server/app/url.ts#L33

The reason you're likely seeing http instead of https is that somewhere in the network stack in front of your Coral pods (load balancer, reverse proxy), it is stripping the https when it redirects the requests to Coral.

@knom
Copy link
Author

knom commented Feb 7, 2024

Hey @nick-funk:
I have a question regarding support.

  • Serverless Hosting: Do you refer to AWS Fargate - or Docker in general being unsupported?
    If Fargate only, what would be a supported AWS Container environment?

  • Networking stacks: likewise :-)

Thanks for your help :-)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants