Resolved Renaming an additional administrator is not reflected in the admin_alias_update event or Action Log: "Login Name" shows the old name as both old and n

[Kaspar]

TITLE
Renaming an additional administrator is not reflected in the admin_alias_update event or Action Log: "Login Name" shows the old name as both old and new value

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE
Plesk Obsidian 18.0.80.8
AlmaLinux 9.8

PROBLEM DESCRIPTION

When an additional administrator account is renamed, the admin_alias_update event carries the old username in both oldValues and newValues for "Login Name". The same wrong values are written to the Action Log. The new username only appears in the account's next event. As a result, neither the Action Log nor extension event listeners (EventListener::handleEvent()) can see that a rename happened, or what the new username is.

The impact:

• Audit trail: the Action Log doesn't record the rename of an administrator account, which is a security-relevant change. Reading the log, the account appears to change name silently between two entries.
• Extensions: they can't track renames through events. An extension that stores data per username can't learn the new name, because neither the CLI nor the XML API exposes the account ID for a later lookup.

STEPS TO REPRODUCE

PSA_PASSWORD='NJJWAoPV7604YncvXCPNF7i3yQfka87RZbEtGQjqTX8UM3xefsfk73A' plesk bin admin_alias --create bugrepro-old -passwd "" -email [email protected] -contact 'Bug Repro'
plesk bin admin_alias --update bugrepro-old -login bugrepro-new
plesk bin admin_alias --update bugrepro-new -contact 'Bug Repro 2'
plesk bin admin_alias --remove bugrepro-new

Then check the values at Tools & Settings › Action Log

ACTUAL RESULT
The update event for the rename has "Login Name" old = bugrepro-old, new = bugrepro-new.

EXPECTED RESULT
The rename event has old = bugrepro-old and new = bugrepro-old. The next, unrelated update then shows bugrepro-new as both old and new.

ANY ADDITIONAL INFORMATION

The same thing happens when the rename is combined with other changes in one call, for example --update <login> -login <new> -passwd "" -enabled true: the status change is reported correctly, but the rename is not. The rename itself succeeds, and admin_aliases.login has the new value.

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug

 

[Sebahat.hadzhi]

Hi, Kaspar. Thank you for the report. I opened an internal case for further review of the behavior. I will follow up with more details as soon as possible.

 

[Sebahat.hadzhi]

Kaspar, the behavior was confirmed as a bug identified with ID PPPM-15543. The fix is ready and should be introduced in the upcoming Plesk release. Thank you for bringing our attention to the issue.

 

[Sebahat.hadzhi]

The issue with the "Login Name" change reflection has been fixed as of Plesk Obsidian 18.0.82:

Fixed an issue where, after changing the username of an additional administrator account via the plesk bin admin_alias --update command, the Action Log entry would show the old username as both the old and the new values. (PPPM-15543)

Thank you once again for bringing our attention to it.