You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm working on setting up oidc authentication for shinyproxy through AWS Cognito, but as part of the handshake, the redirect uri gets formatted with http instead of https causing an error. I saw in the documentation that I need forward-headers-strategy: native in the server part of the yaml, but that still results in http being used in the redirect url. X-Forward-For and X-Forward-Proto both appear in the request logs, but X-Forward-Proto is still set to http. I saw several other people had the same/similar issue, but it doesn't look like there is a solution on those threads.
I have an application load balancer (not a NLB) in front of the ec2 running shinyproxy to handle the https encryption since my ec2 is running on a private network. Is that part of the problem? And if so, how would I get around this? Any help is much appreciated!
The text was updated successfully, but these errors were encountered:
It seems your setup is correct, except that you mention X-Forward-Proto has the value http. ShinyProxy uses this value to know whether to start the generated url with http or https. We have used ALB before, and didn't experience this issue. Did you configure an ACM cert in ALB? It could also be worth to check whether ALB enforces a redirect to HTTPS.
Thank you so much for the quick reply! I do have an ACM cert in the ALB and I think the HTTPS redirect is fine. If I go back to simple authentication, the app gets served up on HTTPS just fine. I also have a traefik dashboard that is reachable over HTTPS too.
I am running shinyproxy with docker swarm for scaling, so I am using a little bit older version of the shinyproxy image since it looks like the latest image doesn't work well with docker swarm. Could that be part of the problem? If I change images to the latest shinyproxy version, the container fails to start and I get the exception "Backend is not a Docker Swarm" in the logs. Thank you again for the help!
I'm working on setting up oidc authentication for shinyproxy through AWS Cognito, but as part of the handshake, the redirect uri gets formatted with http instead of https causing an error. I saw in the documentation that I need
forward-headers-strategy: native
in the server part of the yaml, but that still results in http being used in the redirect url.X-Forward-For
andX-Forward-Proto
both appear in the request logs, butX-Forward-Proto
is still set to http. I saw several other people had the same/similar issue, but it doesn't look like there is a solution on those threads.I have an application load balancer (not a NLB) in front of the ec2 running shinyproxy to handle the https encryption since my ec2 is running on a private network. Is that part of the problem? And if so, how would I get around this? Any help is much appreciated!
The text was updated successfully, but these errors were encountered: