[
https://issues.apache.org/jira/browse/NIFI-15499?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18054311#comment-18054311
]
Craig Patrick commented on NIFI-15499:
--------------------------------------
Hi [~exceptionfactory] - you _could_ source this from provider yes, but my idea
was more to store this relevant and local to NiFi. We do store user information
in NiFi (ID for example) in order to be able to authorise users to certain
parts of the system, and so I guess my idea was more along the lines of:
Adding a display name...
!image-2026-01-26-08-49-49-575.png!
This could then be stored within the users.xml file (if set)...
{code:java}
er identifier="uuid-****" identity="cn=ldap_identity,ou=...,ou=..."
display_name="John Doe"/> {code}
If the display name is set, then we can obtain it and use it, if not we can use
the identity.
With regards to where this is handy, in my use case there are a couple of ideas:
-> In the commit message we send to Bitbucket via Registry where the user is
appended to the end of the message. At the moment it adds the identity which in
some cases might not be anything meaningful for the person checking the
commits, and could be something like:
!image-2026-01-26-08-55-18-593.png!
Ideally, something like this would be much better:
!image-2026-01-26-08-56-52-159.png!
Now, whether that information comes from Registry or NiFi I'm not sure, but if
we move to direct git integrations within NiFi away from Registry then this
will definitely be the case.
Other use cases would be in things like the Flow Configuration History, where
we could something like:
!image-2026-01-26-08-59-09-412.png!
Again, this would be much nicer if we could see an actual name or something
more verbose for us:
!image-2026-01-26-09-00-10-655.png!
This is just a couple of examples where it could be used, but it also means
that should the person access a role change but the LDAP log in and everything
else remains the same, we can change a display name and it keeps everything
else the same. Not sure if this is feasible, but is another possible use case
> Add ability to have a Display Name for users in NiFi
> ----------------------------------------------------
>
> Key: NIFI-15499
> URL: https://issues.apache.org/jira/browse/NIFI-15499
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Core UI
> Environment: All
> Reporter: Craig Patrick
> Priority: Major
> Attachments: image-2026-01-26-08-49-49-575.png,
> image-2026-01-26-08-55-18-593.png, image-2026-01-26-08-56-52-159.png,
> image-2026-01-26-08-59-09-412.png, image-2026-01-26-09-00-10-655.png
>
>
> At the moment, throughout NiFi the user information is displayed as what
> could be considered their "username" - that is, the information they use to
> log in. In some instances this might be convoluted, and in others is
> difficult to comprehend. As an example, for our integrations all of our users
> are LDAP and so we have things like:
> CN=my_user,OU=... etc etc.
> It would be nice if we could extend the user interface so we could add a
> "Display Name" which would be used throughout the UI so instead of the above,
> we could even name people as "Steve in Accounts" and clearly see who is
> making changes to processes, or who is updating flows - especially if
> usernames are even more obfuscated and convoluted.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
