Rocket.chat: (3.9.3) The name in the sidebar is not updated when changing the LDAP search attribute

[aleadco]

Description:

I have modified the search attribute to show the full name of the user, previously I used giveName and I switched to using displayName.
The output result is correct in the conversation but in the column to the right it is not updated.

Steps to reproduce:

1. Admin
2. LDAP
3. {"giveName":"name", "mail":"email"} by {"displayName":"name", "mail":"email"}

Expected behavior:

Actual behavior:

Update the display name of the users

Server Setup Information:

• Version of Rocket.Chat Server: 3.6.3
• Operating System: Ubuntu Server
• Deployment Method: /tar/
• Number of Running Instances: 1
• DB Replicaset Oplog: Yes
• NodeJS Version: v12.18.3
• MongoDB Version: 4.0.20

Client Setup Information

It is not updated in any of the access routes, Android, PC, Browser, etc.

Additional context

Relevant logs:

[aleadco]

Apparently this does not happen with new registered users, only with those who are already in the system.

[ankar84]

As I remember that data changes for existing users if they logoff-login.
And during sync, I think.

[aleadco]

Hello @ankar84 , I thought that at first but it is not what happens, I have already verified it and for existing users it does not update even if you exit the session as is the case of the image that I attached where you can see only the name on the left and to the right the full name (I covered the last names for privacy).

[aleadco]

Hello @ankar84 , in this image is another example of a user who was already registered but had not accessed the service for a few months. With this user we try to exit the session and re-enter, not your effect. I emphasize again that the problem is in the list of private chats, within each chat the user name information if it is displayed correctly updated. We also tried from the Android app, we cleared the cache, nothing at all.

[ankar84]

Hello @ankar84 , in this image is another example of a user who was already registered but had not accessed the service for a few months.

Ok, so I guess it's a new problem, because in previous versions if I changed User Data Field Map from Name to DisplayName all users updated their appearance after logoff-login (and I think after full sync too)

[aleadco]

I tried to force sync and did not get good results either. As I mentioned at the beginning, only the new users are updated, the existing ones are not.

[bhdung]

My problem is same without using LDAP.

When user changed his name, the sidebar private chat updated his new "Name".
But after some short time or reload in desktop app, his recent "Name" gets ignored and the sidebar private chat shows his previous "Name" insteal

[aleadco]

My problem is same without using LDAP.

When user changed his name, the sidebar private chat updated his new "Name".
But after some short time or reload in desktop app, his recent "Name" gets ignored and the sidebar private chat shows his previous "Name" insteal

If exactly, the interesting thing is that the problem is only in the sidebar.

[bhdung]

My problem is same without using LDAP.
When user changed his name, the sidebar private chat updated his new "Name".
But after some short time or reload in desktop app, his recent "Name" gets ignored and the sidebar private chat shows his previous "Name" insteal

If exactly, the interesting thing is that the problem is only in the sidebar.

Yah. Exactly. I found problem in the sidebar and in the threads conversation don't updated new name of users. I tested in cloud Rocket.Chat (https://open.rocket.chat/) got problem same

[aleadco]

This issue is not yet resolved with the 3.8.0 update

[bhdung]

This issue is not yet resolved with the 3.8.0 update

Hi aleadco,

I found code will update fullname user in subscription's collection on database, you can use it in mongo shell. I did do that and fixed my problem. Remember backup your database before you run

var subscriptions = db.rocketchat_subscription.find({
t: 'd',
});

subscriptions.forEach(function (subscription) {
var user = db.users.findOne({
username: subscription.name,
}, { name: 1 });
if (!user) {
return;
}
db.rocketchat_subscription.update({
_id: subscription._id,
}, {
$set: {
fname: user.name,
},
});
});

[adolfombarros]

Description:

I have modified the search attribute to show the full name of the user, previously I used giveName and I switched to using displayName.
The output result is correct in the conversation but in the column to the right it is not updated.

Steps to reproduce:

1. Admin
2. LDAP
3. {"giveName":"name", "mail":"email"} by {"displayName":"name", "mail":"email"}

Expected behavior:

Actual behavior:

Update the display name of the users

Server Setup Information:

• Version of Rocket.Chat Server: 3.6.3
• Operating System: Ubuntu Server
• Deployment Method: /tar/
• Number of Running Instances: 1
• DB Replicaset Oplog: Yes
• NodeJS Version: v12.18.3
• MongoDB Version: 4.0.20

Client Setup Information

It is not updated in any of the access routes, Android, PC, Browser, etc.

Additional context

Relevant logs:

18469 The same issue !

We got the same issue in our environment with rocket.chat 3.9.1 and mongodb 4.0.20.

We use the following mask to compose the names of users on rocket.chat: #{givenName}.mat.#{sn}

Users log in using sAMAccountName.

This configuration works perfectly synchronized with the LDAP server.

However, when changing the givenname or surname on the LDAP server, we got this issue with old.username in the left list and chat titles.

Looking forward to a definitive solution.