-
Notifications
You must be signed in to change notification settings - Fork 26
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
[FEATURE] Support preemptive basic auth in JDBC driver #28
Comments
Hello Any update for this ? We activate SAML on our AWS Opensearch cluster and we have the same issue. |
Thanks for reporting the issue! Unfortunately, we haven't worked on this yet. @acarbonetto Could you take a look when you have time? See if we can add this to our roadmap. Thanks! |
Hello Any updates on this issue? We faced the same issue as well when we enabled OIDC along with basic authentication having ( |
Same here |
@dai-chen I think this was really resolved in a fork Bit-Quill#4 |
@lucasfcnunes I think so. Probably I can close this. Thanks! |
@lucasfcnunes Sorry I misunderstood what you posted. So it seems PR was not merged to main repo yet? |
[Catch All Triage - 1, 2] |
Is your feature request related to a problem?
Currently basic auth is non-preemptive that expect an authenticate header (
WWW-Authenticate: Basic ...
) from the server. There is problem when server responds something else, for example, an OpenSearch cluster with SAML enabled returnsWWW-Authenticate: X-Security-IdP
instead. This fails the basic auth request with a 401 HTTP error.What solution would you like?
One solution is switch to preemptive auth and enforce it all the time. The impact of this needs to be evaluated carefully.
What alternatives have you considered?
Alternatively, provide a configuration for user to choose which auth mode to use. This may be safer and more flexible option compared with enforcing preemptive auth.
Do you have any additional context?
The text was updated successfully, but these errors were encountered: