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

[FIX] Always set LDAP properties on login #7472

Merged
merged 1 commit into from
Jul 14, 2017
Merged

Conversation

sampaiodiego
Copy link
Member

@sampaiodiego sampaiodiego commented Jul 11, 2017

@RocketChat/core

This PR will prevent new LDAP logins from being stuck even if Merge existing users is disabled.

For users that currently cannot log in (see #7429 and #7405) you'll need to enable Merge existing users.

@sampaiodiego sampaiodiego added this to the 0.57.2 milestone Jul 11, 2017
@sampaiodiego sampaiodiego requested a review from rodrigok July 11, 2017 21:17
@engelgabriel engelgabriel temporarily deployed to rocket-chat-pr-7472 July 11, 2017 21:18 Inactive
@sampaiodiego sampaiodiego changed the title [WIP] Always set LDAP properties on login [FIX] Always set LDAP properties on login Jul 12, 2017
@rodrigok rodrigok merged commit a44ae3f into develop Jul 14, 2017
@rodrigok rodrigok deleted the always-set-ldap-property branch July 14, 2017 14:16
rodrigok added a commit that referenced this pull request Jul 14, 2017
[FIX] Always set LDAP properties on login
@adipose
Copy link

adipose commented Apr 2, 2018

Using .62.2 I was forced to enable the "merge" option for some users to be able to login. This was a fresh install of RocketChat server, and the users had never logged in before today, but until I chose the "merge" option, they could only login using their email address. Since there should have been nothing new to "merge," it sure seems like this is still some sort of LDAP bug.

Also, disabling/reenabling Avatar sync had no effect either way.

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 this pull request may close these issues.

4 participants