-
Notifications
You must be signed in to change notification settings - Fork 25k
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
Support swapping the user context to the secondary auth user for named actions #106613
Conversation
Pinging @elastic/es-security (Team:Security) |
|
||
public class SecondaryAuthActionsPlugin extends Plugin implements SecondaryAuthActions { | ||
public Set<String> get() { | ||
return Set.of("cluster:admin/xpack/security/user/authenticate", "indices:admin/get"); |
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.
note - this is a test only plugin.
...urity/src/main/java/org/elasticsearch/xpack/security/action/filter/SecurityActionFilter.java
Outdated
Show resolved
Hide resolved
@elasticmachine run elasticsearch-ci/part-1-fips (failure instance of #106752) |
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.
LGTM
This commit adds the ability to define specific actions that are required to be executed as the secondary authenticated user. When actions are defined as secondary auth actions, then the secondary authentication headers (and subsequent authentication) are required to call those actions and the authorization is based on the secondary user. The SPI hook to define which actions are required is intended for internal only use only.