[ 
https://issues.apache.org/jira/browse/NIFI-14930?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18018650#comment-18018650
 ] 

ASF subversion and git services commented on NIFI-14930:
--------------------------------------------------------

Commit f40e3f59e315593a96dcbb49ff2d74b658c00ddb in nifi's branch 
refs/heads/main from David Handermann
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=f40e3f59e3 ]

NIFI-14930 Added logging for Tenant User and Group operations

Signed-off-by: Pierre Villard <[email protected]>

This closes #10281.


> Enhance Logging for Local User Account Creation/Deletion in Apache NiFi
> -----------------------------------------------------------------------
>
>                 Key: NIFI-14930
>                 URL: https://issues.apache.org/jira/browse/NIFI-14930
>             Project: Apache NiFi
>          Issue Type: Wish
>            Reporter: Tatiana Malinina
>            Assignee: David Handermann
>            Priority: Minor
>              Labels: security
>         Attachments: image-2025-09-02-16-38-02-935.png
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Currently, Apache NiFi does not provide sufficient logging details for 
> operations involving the creation and deletion of local user accounts. There 
> is no clear record in the logs indicating:
>  * *Which user account* was created or deleted
>  * *Who performed* the operation
>  * *When* the action occurred
> This information is critical for auditing and security purposes.
> *Proposed Enhancement:*
> Enhance NiFi's logging mechanism so that when a local user account is created 
> or deleted, the system logs the following information at an appropriate log 
> level (e.g., INFO):
>  * Timestamp of the event
>  * Username of the account being created or deleted
>  * Identity of the user who performed the operation (e.g., admin username or 
> identity provider information)
>  * Operation type: creation or deletion



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to