-
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
[Osquery] Fix issue with plugin initialization #100208
[Osquery] Fix issue with plugin initialization #100208
Conversation
@elasticmachine merge upstream |
Pinging @elastic/security-asset-management (Team:Asset Management) |
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.
🔌 📦
…lugin-setupp # Conflicts: # x-pack/plugins/osquery/public/plugin.ts
Pinging @elastic/fleet (Team:Fleet) |
const isSuperUser = osqueryContext.security.authc | ||
.getCurrentUser(request) | ||
?.roles.includes('superuser'); |
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.
I am wondering if we should expose a method in Fleet to do that something like isAuthorized(request)
. I think in the future we want to allow non superuser with enough permissions.
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.
that would be helpful @nchaulet. We are also working on allowing to use Osquery for non superuser
@elasticmachine merge upstream |
💚 Build SucceededMetrics [docs]Public APIs missing comments
Async chunks
Page load bundle
History
To update your PR or re-run it, just comment with: |
Summary
Fixes #100285