Remove SecurityManager code from ingest attachment #127291
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Now that SecurityManager is gone, there is no longer a need for a specialized access control context for interacting with tika.
rjernst
added
>refactoring
auto-backport
Collaborator
|
Pinging @elastic/es-core-infra (Team:Core/Infra) |
Collaborator
💚 Backport successful
|
rjernst
added a commit
to rjernst/elasticsearch
that referenced
this pull request
Apr 24, 2025
Now that SecurityManager is gone, there is no longer a need for a specialized access control context for interacting with tika.
elasticsearchmachine
pushed a commit
that referenced
this pull request
May 1, 2025
Now that SecurityManager is gone, there is no longer a need for a specialized access control context for interacting with tika. Co-authored-by: Elastic Machine <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Now that SecurityManager is gone, there is no longer a need for a specialized access control context for interacting with tika.
Relates to ES-10922