-
Notifications
You must be signed in to change notification settings - Fork 25.4k
Allow configuring SAML private attributes #133154
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
Allow configuring SAML private attributes #133154
Conversation
This PR is twofold: - it adds a new `secure_attributes` setting to the SAML realm, and - introduces extension point that allows providing a custom `SamlAuthenticateResponseHandler` The `secure_attributes` setting can be used to define which SAML attributes should be treated as secure. This implies that these attributes should not be logged, or returned as part of user's metadata when `populate_user_metadata` is set to `true`.
Hi @slobodanadamovic, I've created a changelog YAML for you. |
…ure-attrtibutes # Conflicts: # x-pack/plugin/security/src/main/java/org/elasticsearch/xpack/security/Security.java
...n/core/src/main/java/org/elasticsearch/xpack/core/security/authc/saml/SamlRealmSettings.java
Outdated
Show resolved
Hide resolved
*/ | ||
public static final Function<String, Setting.AffixSetting<List<String>>> SECURE_ATTRIBUTES = (type) -> Setting.affixKeySetting( | ||
RealmSettings.realmSettingPrefix(type), | ||
"secure_attributes", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is secure
the right word? It implies that other attributes are "insecure".
Maybe private
or confidential
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the callout. I was on the fence between secure
, private
and secret
. Went with secure as it seemed like a better fit (at least implementation wise). I'm okay with private
. Technically, the main goal is to allow hiding certain attributes and treating them as private only.
...lugin/security/src/main/java/org/elasticsearch/xpack/security/authc/saml/SamlAttributes.java
Outdated
Show resolved
Hide resolved
Pinging @elastic/es-security (Team:Security) |
…/elasticsearch into saml-secure-attrtibutes
This PR is twofold: - adds a new `private_attributes` setting to the SAML realm, and - introduces extension point that allows providing a custom `SamlAuthenticateResponseHandler` The `private_attributes` setting can be used to define which SAML attributes should be treated as private. This implies that these attributes will not be logged or returned as part of user's metadata when `populate_user_metadata` is set to `true`.
This PR is twofold:
private_attributes
setting to the SAML realm, andSamlAuthenticateResponseHandler
The
private_attributes
setting can be used to define which SAML attributes should be treated as private. This implies that these attributes will not be logged or returned as part of user's metadata whenpopulate_user_metadata
is set totrue
.