Issue Summary

My team has successfully deployed redash v10 in AWS ECS Fargate + RDS + Elasticache, deployed in a private vpc with load balancers (one day I might need to share what we did I assume it will be helpful for the community).

We are in the testing phase now. Our redash database was upgraded from our v5 production database. On production, we use SAML for authentication. In our test environment, we for now just use remote login, however, we are ready to share the test app with other users in the organization. So I turned on username/password login and turned off remote login. But now I see an empty login screen (see below)

image

My questions

  1. I scanned through the code and I believe my environment variables are setup correctly
REDASH_SAML_AUTH_TYPE = 
REDASH_SAML_ENCRYPTION_CERT_PATH = 
REDASH_SAML_ENCRYPTION_PEM_PATH = 
REDASH_SAML_ENTITY_ID = 
REDASH_SAML_METADATA_URL = 
REDASH_SAML_NAMEID_FORMAT = 
REDASH_SAML_SCHEME_OVERRIDE = 
REDASH_SAML_SSO_URL = 
REDASH_SAML_X509_CERT = 
SAML_ENCRYPTION_ENABLED = false
SAML_ENCRYPTION_PEM_PATH = 
SAML_SCHEME_OVERRIDE =
REDASH_PASSWORD_LOGIN_ENABLED = true
REDASH_LDAP_LOGIN_ENABLED = false
REDASH_REMOTE_USER_LOGIN_ENABLED = false
GOOGLE_CLIENT_ID = 
GOOGLE_CLIENT_SECRET = 

Is the login screen empty due to the database setup? What am I missing?

  1. Is this even possible in redash v10, and also given that our backup database comes from a SAML-only prod database?

Technical details:

  • Redash Version: Image 10.0.0.b50363
  • Browser/OS: Chrome, macOS Big Sur
  • How did you install Redash: docker

Thank you in advance

2 Likes

I’m working to reproduce this on my end. One thing I wonder: did you change any of the settings in Redash itself (not the environment variables)?

Hi @jesse Thank you for your help

We found out what was going on. The environment variables were setting up ok but the organization setting in the database already had this (kinda what you hinted at)

select settings from organizations
-- {"google_apps_domains": [], "settings": {"auth_password_login_enabled": false, "beacon_consent": false}}

The problem is in the UI Changing that was not allowed. redash/PasswordLoginSettings.jsx at release/10.0.x · getredash/redash · GitHub

So I resorted to just updating that setting straight on the organizations table

and Now I can see the password page

2 Likes

I ran into the same issue when trying to reproduce. I think the environment variables are ignored if there is a value in the database already (which isn’t obvious and probably should be).

Thanks for posting your solution!

1 Like