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

When an incoming message is displayed username, not name #11776

Closed
nicexe2e4 opened this issue Aug 14, 2018 · 12 comments
Closed

When an incoming message is displayed username, not name #11776

nicexe2e4 opened this issue Aug 14, 2018 · 12 comments

Comments

@nicexe2e4
Copy link

nicexe2e4 commented Aug 14, 2018

Description:

Authentication via LDAP server
User Data Field Map { "cn":"name", "mail":"mail"}
Use Real Name True
Problem appeared after updating from 0.66.3 to 0.68.3
Update to 0.69.0 not fixed the problem

Steps to reproduce:

  1. Login via test acc and type direct message to real acc

image
2. Login via real acc and read direct message from test acc

image

Expected behavior:

To see real name in a direct messages, not username.

Server Setup Information:

  • Version of Rocket.Chat Server: 0.68.4
  • Operating System: 4.15.15
  • Deployment Method: tar
  • NodeJS Version: 8.11.2
  • MongoDB Version: 3.6.3
@crazy-max
Copy link
Contributor

crazy-max commented Aug 20, 2018

Same issue for me on 0.69.0

@rsuguiura
Copy link

Same issue for me too. Using the Official Rocket.Chat docker deployment image.

@altapo
Copy link

altapo commented Aug 24, 2018

+1

@Gummikavalier
Copy link

Gummikavalier commented Aug 28, 2018

Saw this too with 0.68.4 at least. Edit: Tested and it happens also on 0.69.0.

@zzeesstt
Copy link

zzeesstt commented Aug 31, 2018

snap: 0.69.0
+1

1 similar comment
@zzeesstt
Copy link

zzeesstt commented Sep 3, 2018

snap: 0.69.0
+1

@dude75
Copy link

dude75 commented Sep 3, 2018

+1 i'm have same bug

@cadetmsv
Copy link

cadetmsv commented Sep 7, 2018

snap: 0.69.0
+1
very not beautiful bug

@borg69
Copy link

borg69 commented Sep 7, 2018

+1 I confirm this bug

@crazy-max
Copy link
Contributor

@borg69 @cadetmsv @dude75 @zzeesstt @alexdriver

If you find your issue already exists, please make relevant comments and add your reaction. Use a reaction in place of a "+1" comment.

👍 - upvote

👎 - downvote

@Gummikavalier
Copy link

Milestone 0.70.0 in #11913 :)

@sampaiodiego
Copy link
Member

fixed by #12154

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests