Skip to content
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

SSO support IdP providers and client secrets on a per database level #120380

Closed
steven-hubbard opened this issue Mar 12, 2024 · 2 comments
Closed
Labels
A-security C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) T-product-security

Comments

@steven-hubbard
Copy link
Contributor

steven-hubbard commented Mar 12, 2024

Would like to be able to provide multiple sets of IdP information where any comma separated list could work for the entire cluster or that we could tie each one to a specific database within the cluster.

Jira issue: CRDB-36656

gz#20644

@steven-hubbard steven-hubbard added the C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) label Mar 12, 2024
@pritesh-lahoti
Copy link
Contributor

@steven-hubbard We are currently working on LDAP-based authentication (#125076), wherein the authentication method could be configured at a cluster/database/user level within the HBA conf.
We believe that should solve for this use-case. Let us know your thoughts.
cc - @kannanlakshmi @dikshant @BabuSrithar

@steven-hubbard
Copy link
Contributor Author

Yes that should handle it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-security C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) T-product-security
Projects
None yet
Development

No branches or pull requests

3 participants