RocketChat / RocketChat/Rocket.Chat

Automatic Avatar using LDAP doesn't provice correct name initials in some cases

Open
#7,949 5 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

area: authentication
Dominant language
TypeScript
Stars
46.1k
Forks
13.9k
Avg merge
3d 3h
Merged PRs (30d)
130

Description

Description:

Using LDAP Connection to an ActiveDirectory.
It's working fine for nearly all users, except for some:

screen

In these cases, it should be GS and ES.

In my case the "Use full name initials" setting doesn't make a difference.
Rocket.Chat then either uses the username or Full Name in LDAP as source.
It's noteworthy, that in my case the username is nearly identical to the Full Name.

Server Setup Information:
  • Version of Rocket.Chat Server: 0.58.1
  • Operating System: Debian 9.1 Stretch
  • Deployment Method(snap/docker/tar/etc): tar
  • Number of Running Instances: 2
  • DB Replicaset Oplog: Yes, 1 ReplicaSet
  • Node Version: 4.8.2
Steps to Reproduce:
  1. Create LDAP user with Full Name like "User User-Name"
  2. Sign in to Rocket.Chat using this user.
  3. Avatar gets auto-generated.
Expected behavior:

Should be "UU" in this example.

Actual behavior:

But is "UN" in this example.

Any idea why ?
Thanks for your answers!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file or test is named. Start by tracing the LDAP sign-in path into automatic avatar generation, then compare how the username and Full Name are selected for initials. Done means the reproduced ActiveDirectory example generates the expected initials, such as UU rather than UN.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
authentication
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.