Project

General

Profile

Actions

User story #6826

open

Implement Display Names additionally to login names

Added by Janos Mattyasovszky almost 9 years ago. Updated about 6 years ago.

Status:
New
Priority:
2
Assignee:
-
Category:
Web - UI & UX
UX impact:
Suggestion strength:
User visibility:
Effort required:
Name check:
Fix check:
Regression:

Description

Please add an additional field to the user management, that would mean the display name.

Example in rudder-users.xml:

  <user name="ts20429" display="Tobias Simons" password="LDAP" role="user" />

This would then be user for greeting, like: "Welcome, Tobias Simons" instead of "Welcome, ts20429".

This Name could also be used in logging, as sometimes when the user is deleted from the AD Backend, it's hard to find out who ts20429 was...

For LDAP enabled, this could be also fetched from an arbitrary attribute of the user entry, like cn or displayName...

Actions #1

Updated by Matthieu CERDA almost 9 years ago

  • Assignee set to François ARMAND
  • Priority changed from N/A to 2
  • Target version set to Ideas (not version specific)

I LOVE this idea !

Assigning to fanf for dispatch

Actions #2

Updated by François ARMAND almost 9 years ago

This is a natural enhancement on user management in Rudder.

Basically, their is three things to manage with user, which are separated from a strict Identity and Access Management, but are generally linked from a data-centric point of view (these are nothing new, but I but then for context):

- user identification: from what you say/know, I can bound to you a set of datas (name, email, etc)
- user authentication: given some protocol and access context, challange the user and issue an authentication token
- user authorization: given some identified user and authentication token, give credentials to do things.

The first two are most of the time company-wide, the last is necessarilly bound to the application (even if the mapping between user and rights is outside the application).

In Rudder, we are only managing rights (in the XML file, no other way for now). We have nothing for identification beyond the scrict minimum identification token used to allows authentication. And authentication is plugable, with defaults connector to the rudder user file and LDAP.

So, what you (naturally) ask is to properly manage user identification, beyond just the pivot attribut used for authentication.

For conclusion: it's on the roadmap, on a not to hight priority for now.

Actions #3

Updated by François ARMAND about 6 years ago

  • Assignee deleted (François ARMAND)
Actions

Also available in: Atom PDF