Skip to content

Conversation

@rullzer
Copy link
Member

@rullzer rullzer commented Nov 20, 2018

Fixes #11146
As documented when it is set to disabled the user can't request a lost
password.

Signed-off-by: Roeland Jago Douma [email protected]

Fixes #11146
As documented when it is set to disabled the user can't request a lost
password.

Signed-off-by: Roeland Jago Douma <[email protected]>
@rullzer
Copy link
Member Author

rullzer commented Nov 20, 2018

/backport to stable14

Copy link
Member

@MorrisJobke MorrisJobke left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tested and works 👍

Copy link
Member

@MariusBluem MariusBluem left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense :)

@MorrisJobke MorrisJobke added 4. to release Ready to be released and/or waiting for tests to finish and removed 3. to review Waiting for reviews labels Nov 20, 2018
@rullzer rullzer merged commit e73bfd5 into master Nov 20, 2018
@rullzer rullzer deleted the fix/11146/respect_disabled_password_reset branch November 20, 2018 14:52
@backportbot-nextcloud
Copy link

backport to stable14 in #12555

@MorrisJobke MorrisJobke mentioned this pull request Nov 22, 2018
7 tasks
Copy link

@HigH-HawK HigH-HawK left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It works as far as it removes the link from the login page but it causes the LDAP function to misbehave.

As mentioned in the forums: https://help.nextcloud.com/t/ldap-error-in-14-0-4-after-changing-lost-password-link-behaviour-bind-failed-50-insufficient-access/42060

When this change is being done and the user enters a wrong password, the user is getting an internal server error and the NC log states that it could not connect to the LDAP server, despite the LDAP server being available as other users could login fine at the same time.

Further testing brought to daylight, that this behaviour only happens if the entered username is part of the LDAP server. If you enter a fictional username and password, it brings up the correct message "wrong password"

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

Labels

4. to release Ready to be released and/or waiting for tests to finish bug regression

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants