[system][auth] Remove deprecated user.name/user.id duplication for IAM events#20353
Open
nicholasberlin wants to merge 1 commit into
Open
[system][auth] Remove deprecated user.name/user.id duplication for IAM events#20353nicholasberlin wants to merge 1 commit into
nicholasberlin wants to merge 1 commit into
Conversation
Contributor
✅ Elastic Docs Style Checker (Vale)No issues found on modified lines! The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
…M events Contract phase of the expand-and-contract migration started in 2.22.0 (#20339): the auth data stream no longer writes the affected account to user.name/user.id for useradd account creation, usermod group membership, userdel deletion, and PAM password change events. The affected account remains in user.target.name (and user.target.id for useradd); user.name on these events is reserved for the acting user, matching ECS semantics. On journald input, useradd events now keep the actor UID from journald metadata in user.id instead of having it overwritten by the created account's UID. Mechanically this deletes the five *_compat processors that 2.22.0 introduced for backward compatibility and regenerates the pipeline test expectations, whose diff is exactly the removal of the duplicated fields. Ships as 3.0.0 with a breaking-change changelog entry so Kibana requires users to acknowledge the change before upgrading. The bundled New users and groups dashboard already reads user.target.* as of 2.23.0.
nicholasberlin
added
breaking change
breaking-change
Integration:system
|
Pinging @elastic/sec-linux-platform (Team:Security-Linux Platform) |
nicholasberlin
force-pushed
the
breaking/system-auth-remove-user-name-duplication
branch
from
July 24, 2026 17:43
a0ff7c3 to
6b7ceb9
Compare
Contributor
Author
|
The deprecation release was here: #20105 (comment) July 24, 2026 Not sure how long of a grace period. |
Contributor
|
✅ All changelog entries have the correct PR link. |
Contributor
🚀 Benchmarks reportPackage
|
| Data stream | Previous EPS | New EPS | Diff (%) | Result |
|---|---|---|---|---|
security |
1751.31 | 1053.07 | -698.24 (-39.87%) | 💔 |
auth |
5154.64 | 3636.36 | -1518.28 (-29.45%) | 💔 |
To see the full report comment with /test benchmark fullreport
💚 Build Succeeded
|
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Important
Merge #20352 (dashboard migration to
user.target.*) first. This PR isbased directly on main and will be rebased once #20352 merges, so the
bundled New users and groups dashboard never ships a version that reads
fields this PR removes.
Proposed commit message
Contract phase of the expand-and-contract migration started in 2.22.0
(#20339): the auth data stream no longer writes the
affected account to
user.name/user.idfor useradd account creation,usermod group membership, userdel deletion, and PAM password change events.
The affected account remains in
user.target.name(anduser.target.idforuseradd);
user.nameon these events is reserved for the acting user,matching ECS semantics. On journald input, useradd events now keep the actor
UID from journald metadata in
user.idinstead of having it overwritten bythe created account's UID.
Mechanically this deletes the five
*_compatprocessors that 2.22.0introduced for backward compatibility and regenerates the pipeline test
expectations, whose diff is exactly the removal of the duplicated fields.
Ships as 3.0.0 with a breaking-change changelog entry so Kibana requires
users to acknowledge the change before upgrading. The bundled New users and
groups dashboard already reads
user.target.*as of 2.23.0 (#20352).Checklist
I have verified that all data streams collect metrics or logs.N/A, pipeline-only changechangelog.ymlfile.I have verified that Kibana version constraints are current according to guidelines.N/AI have verified that any added dashboard complies with Kibana's Dashboard good practicesN/AAuthor's Checklist
references the 2.23.0 dashboard change it introduces).
user.name/user.idfor these IAM events stop matching new data. Thechangelog entry (surfaced by Kibana's upgrade acknowledgment prompt) tells
users what changed, why, and to migrate content to
user.target.*.enough release time has passed between the expand and contract phases for
users to migrate, and hold this PR if not.
How to test this PR locally
Or simulate directly:
with useradd/usermod/userdel/passwd-chauthtok sample events (see
#20105) and verify the affected account appears only in
user.target.*(plusrelated.user), withuser.name/user.idno longerduplicated.
Related issues