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

Bug introduced with Improvement #12891 #14876

Closed
pkolmann opened this issue Jun 26, 2019 · 0 comments · Fixed by #14880
Closed

Bug introduced with Improvement #12891 #14876

pkolmann opened this issue Jun 26, 2019 · 0 comments · Fixed by #14880

Comments

@pkolmann
Copy link
Contributor

Description:

When I added the patch to support the DisplayName as FullName field (see #12347) I used displayName as primary possibility, then CN and last userName.

@kukkjanos with your new patch in #12891 you changed that to CN, userName, displayname.

I have now the issue with our setup, that we don't get a CN from our SAML IdP, but we get username and displayName. Everyone gets now the username set as displayName.

@kukkjanos would it be ok for you to change it to CN, displayName, username or ok if I send a pull request for that?

Thanks
Philipp

Steps to reproduce:

1.) have SAML Login
2.) only have username, displayname, email attributes in the saml reply
3.) login as a new user
4.) See username as Full Name set

Expected behavior:

Use DisplayName as Full Name of new account

Actual behavior:

username is used as Full Name of user

Server Setup Information:

  • Version of Rocket.Chat Server: 1.1.1
  • Operating System: Debian 9
  • Deployment Method: tar
  • Number of Running Instances: 8
  • DB Replicaset Oplog: Enabled
  • NodeJS Version: v8.16.0
  • MongoDB Version: 3.2.11
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

Successfully merging a pull request may close this issue.

1 participant