Add new internal cross-project search user #135531
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
slobodanadamovic
added
>non-issue
:Security/Authorization
|
Pinging @elastic/es-security (Team:Security) |
n1v0lg
approved these changes
Sep 29, 2025
x-pack/plugin/core/src/main/java/org/elasticsearch/xpack/core/security/user/InternalUsers.java
Outdated
Show resolved
Hide resolved
x-pack/plugin/core/src/main/java/org/elasticsearch/xpack/core/security/user/UsernamesField.java
Outdated
Show resolved
Hide resolved
Good question. I thought about this and it's not needed. Reason is because the internal user is unused and thus never gets sent over transport protocol. My plan is to introduce a new transport version and checks when I start using it. |
slobodanadamovic
changed the title
…danadamovic/elasticsearch into cross-project-access-internal-user
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.
This PR introduces a dedicated
_cross_project_searchuser to perform internal orchestration actions for cross project operations, like establishing remote cluster handshakes, cancelling cross cluster searches, etc...