-
Notifications
You must be signed in to change notification settings - Fork 282
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
[BUG] SAML auth is broken after upgrade from 2.11.0 to 2.18.0 #4911
Comments
@timur-ND Are there any other authenticators configured in the |
Also enabled Basic Auth, but challenge is set to False:
All other methods (ldap, clientcert_auth_domain, jwt_auth_domain, proxy_auth_domain,kerberos_auth_domain) is disabled (http_enabled: false). Actually, after restart, I found this in the logs. Seems like something is wrong:
|
Seems my exchange_key was incorrect or idk.
Now seems ok, but strange, this key was the same all the time. Looks like before the upgrade OpenSearch didn't recognize key and somehow it worked well. After the upgrade, the key was no longer valid. |
Describe the bug
Hello. I faced an issue with SAML authorization after upgrade Opensearch and Opensearch Dashboards from 2.11.0 to 2.18.0. I have 3 OpenSearch nodes, I'm using Azure AD and everything was working fine until I upgraded to the new version. Nothing has changed on the configuration side (opensearch-security/config.yml). After trying to log it, I get
{"statusCode":500,"error":"Internal Server Error","message":"Internal Error"}
(uri - /auth/saml/login?redirectHash=false&nextUrl=%2F)On the server side, in Opensearch Dashboards logs, I see this:
On the Opensearch side I see this in the logs:
[2024-11-15T14:01:48,617][WARN ][o.o.s.a.BackendRegistry ] [*****] Authentication finally failed for null from 10.97.3.81:50628
I can login using Basic Auth, since it's enabled. I can't rollback because index version seems incompatible for old Opensearch versions.
My SAML config:
My Opensearch-dashboards configuration:
I hope you can help me. Thank you in advance!
Related component
Other
To Reproduce
Expected behavior
SAML authentication should work the same as before the upgrade.
Additional Details
Plugins
Please list all plugins currently enabled.
Screenshots
If applicable, add screenshots to help explain your problem.
Host/Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: