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
hello, I am not able to configure redash by https with google oauth, it is currently installed with helm chart in AWS eks with http and in front there is an aws NLB, when trying to pass the NLB to https (it performs the ssl/tcp termination) when it comes to When browsing the URL, redash always tries to redirect to http, I don't know if there is something that can be done like the option that already exists for REDASH_SAML_SCHEME_OVERRIDE so that flask can build the URLs with Https correctly and that it will have a good time with google oauth
The text was updated successfully, but these errors were encountered:
Hi @arikfr, It is possible that the team can review this of the change of schema from https to http when there is an AWS NLB as a proxy in front of the Redash deployed with helm chart, I don't know if there is already a parameter that can be used to allow this and not rewrite the URIs in http
hello, I am not able to configure redash by https with google oauth, it is currently installed with helm chart in AWS eks with http and in front there is an aws NLB, when trying to pass the NLB to https (it performs the ssl/tcp termination) when it comes to When browsing the URL, redash always tries to redirect to http, I don't know if there is something that can be done like the option that already exists for REDASH_SAML_SCHEME_OVERRIDE so that flask can build the URLs with Https correctly and that it will have a good time with google oauth
The text was updated successfully, but these errors were encountered: