-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
[Security Solutions] Move authentication UI and hooks to 'public/common' #128924
Conversation
Pinging @elastic/security-threat-hunting (Team:Threat Hunting) |
Pinging @elastic/security-solution (Team: SecuritySolution) |
c9ea844
to
ecf906c
Compare
@elasticmachine merge upstream |
3db8867
to
dcb1c49
Compare
x-pack/plugins/security_solution/common/search_strategy/security_solution/users/index.ts
Outdated
Show resolved
Hide resolved
|
||
export enum AuthStackByField { | ||
userName = 'user.name', | ||
hostName = 'host.name', |
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 the AuthStackByField.hostName
ever used? I only see it in tests. It seems we always stack by userName?
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.
Yes, you are right. Only user.name
is being used. However, host.name
is necessary for this issue: #129047
@elasticmachine merge upstream |
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 ✅
e1bd3cc
to
f8cd090
Compare
💚 Build SucceededMetrics [docs]Module Count
Async chunks
Page load bundle
History
To update your PR or re-run it, just comment with: cc @machadoum |
issue: #128362
Summary
public/common
stackedByField
to the authentication server. It will be used for the User details pageWhat to test it?
usersEnabled
flag)usersEnabled
flag)Checklist