-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Okta SAML log in isn't working after upgrade to v25.1.0 #7333
Comments
Okta SAML is working fine for me on 25.1 -- maybe check that your secrets didn't get overwritten? |
Do you mean the SAML settings under the Settings > General tab? |
For some reason the redash-server container log giving that it's not succeed to parse the AudienceRestrictions even though I made sure that it's configured on the correct AudienceRestrictions. XML parse error: AudienceRestrictions conditions not satisfied! (Local entity_id=https://my-company.okta.com/app/exkdhzjhrbHkCecvh5d7/sso/saml) |
Update, I've setup a brand new redash server with the setup.sh script, and it created a redash compose with the redash v[10.1.0.b50633] image. I've configured a new okta app for the SAML Login, and the SAML login worked as expected. @BowlesCR How did you perform the upgrade from v10 to v25? |
My install is on kubernetes via Helm chart. It looks like my SAML config is passed in the helm chart values (equivalent to env vars in your Docker Compose), so its very possible that there is some breaking change for configs stored in the DB that wouldn't impact my install. |
@BowlesCR Can you share the helm-chart / documentation that you used for setting the redash via helm-chart on eks? |
I'm using the community-maintained "official" chart: https://github.com/getredash/contrib-helm-chart and overriding |
Issue Summary
After upgrading the V25 the SAML connection stopped working.
Steps to Reproduce
Tried to re-configure the SAML Connection to Okta but it still didn't let me log into redash with the Okta SAML.
On a specific redash server that on v10 the SAML still working
Technical details:
The text was updated successfully, but these errors were encountered: