Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Real name resolving in channel member selection dialog #21480

Closed
Gummikavalier opened this issue Apr 7, 2021 · 1 comment
Closed

Real name resolving in channel member selection dialog #21480

Gummikavalier opened this issue Apr 7, 2021 · 1 comment

Comments

@Gummikavalier
Copy link

Description:

Many other real name resolving issues have been and are being resolved, so I'll also report the specific issue with channel member selection dialog.

This issue is inconvenient on systems that get illegible provisioned usernames from SAML and Oauth endpoints and rely mainly on the real name to tell people apart.

Steps to reproduce:

  1. Enable Use Real Name under Administrator -> Layout -> User Interface
  2. Create a user with an illegible username (here 099fnd2ee) and add a real name to the user (here Test Account)
  3. Invite the user to a channel

Expected behavior:

After selecting the name in the channel add user dialog, real name is shown in the box after the selection.

To be exact, for the security reasons (several users with the same name), both values could be shown during and after making the selection.

Actual behavior:

After selecting the real name from the list, it transforms into a username in the box with already selected users, making over viewing especially bigger selection impossible just before confirming the selections.

Selecting one user by their real name:
Screenshot from 2021-04-07 17-31-33

After the selection the real name transforms into a username:
Screenshot from 2021-04-07 17-31-50

The report after the user has been added also shows the username instead of the real name. User can find out whether the addition of correct person succeeded only by cross referencing the name and the account elsewhere (search for instance).
Screenshot from 2021-04-07 17-32-11

Server Setup Information:

  • Version of Rocket.Chat Server: 3.12.3
  • Operating System: CentOS7
  • Deployment Method: tar
  • Number of Running Instances: 20
  • DB Replicaset Oplog: Yes
  • NodeJS Version: 12.18.4
  • MongoDB Version: 4.0

Client Setup Information

  • Desktop App or Browser Version: Any web browser
@Gummikavalier
Copy link
Author

Closing as fixed.

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

No branches or pull requests

1 participant