LDAP users can't connect sync client 9.0.4 to server 11.0.1 about seahub HOT 5 CLOSED

We will include it in the next release in about two weeks.

from seahub.

I can reproduce it:

Works:

curl -X POST -F '[email protected]' -F 'password=secret' https://seafile.domain.com/api2/auth-token/
{"token":"8e29471fdd10bad0f998b8138a74a80f70e44e8b"}

Doesn't:

curl -X POST -F '[email protected]' -F 'password=secrettoo' https://seafile2.domain.com/api2/auth-token/
{"non_field_errors":["Unable to login with provided credentials."]}

from seahub.

The error message Unable to login with provided credentials. seems to be created in https://github.com/haiwen/seahub/blob/master/seahub/api2/serializers.py#L88.
Some lines ago in https://github.com/haiwen/seahub/blob/master/seahub/api2/serializers.py#L82 the ccnet_api.get_primary_id(username) is called, apparently to get the primary ID.

Isn't a big change in Seafile 11 the use of Python instead of C code for LDAP access? Might the problem derive from here? At least it matches with the observation, that only LDAP accounts have this issue - even if login via web interface works.

from seahub.

Thanks for reporting the issue. We can reproduce the problem. It should be fixed soon.

from seahub.

Looks like d4f93eb is a fix? This was was fast! What do you think when it will be included in a released version?

Edit: I tested the fix and it works: 👍

from seahub.