Skip to content

Fixed #18135 - only unset sensitive variables in the web UI importer#18439

Merged
snipe merged 1 commit intodevelopfrom
#18135-better-handle-cli-importer-permissions
Jan 15, 2026
Merged

Fixed #18135 - only unset sensitive variables in the web UI importer#18439
snipe merged 1 commit intodevelopfrom
#18135-better-handle-cli-importer-permissions

Conversation

@snipe
Copy link
Copy Markdown
Member

@snipe snipe commented Jan 14, 2026

This should fix #18135, where cli user imports were failing because of the added security check to make sure the acting user can perform actions on other users that could compromise security (changing a superusers password or email, etc.)

This gets a little tricky because while the Web UI knows who the authenticated user is, the command line importer has no real way of knowing that (since a cli session is by nature unauthenticated - there is no session.)

This change checks to see if the user is authenticated (meaning it's being run via CLI) and then also uses the gate to check that the authenticated user can change those sensitive fields.

@snipe snipe changed the title Fixed #18135 - only unset variables if the user is authenticated (Web UI) Fixed #18135 - only unset sensitive variables if the user is authenticated (Web UI) Jan 14, 2026
@snipe snipe changed the title Fixed #18135 - only unset sensitive variables if the user is authenticated (Web UI) Fixed #18135 - only unset sensitive variables in the web UI importer Jan 14, 2026
@snipe snipe requested a review from uberbrady January 14, 2026 13:15
@snipe snipe merged commit 04f4f5b into develop Jan 15, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant