Ah, one more thing, maybe this will also help identifying the problem: I am using SSO functionality which also doesn’t work in 8.x version but it works in 7.x version.
My configuration in
ENABLE_REMOTE_USER_AUTHENTICATION = True
# Optional, HTTP header, which is configured in your web server conf file,
# used for Seafile to get user's unique id, default value is 'HTTP_REMOTE_USER'.
REMOTE_USER_HEADER = 'HTTP_REMOTE_USER'
# Optional, whether to create new user in Seafile system, default value is True.
# If this setting is disabled, users doesn't preexist in the Seafile DB cannot login.
# The admin has to first import the users from external systems like LDAP.
REMOTE_USER_CREATE_UNKNOWN_USER = False
# Optional, whether to activate new user in Seafile system, default value is True.
# If this setting is disabled, user will be unable to login by default.
# the administrator needs to manually activate this user.
REMOTE_USER_ACTIVATE_USER_AFTER_CREATION = True
As per my understanding, when SSO is used, the password is not validated, which would mean the LDAP system is not invoked. But instead, the Seafile application would check the user from HTTP header
HTTP_REMOTE_USER against its own database.
When trying to login with SSO, in version 8.0.x, I get the error
Error, new user registration is not allowed, please contact administrator.
Which makes sense, considering that
REMOTE_USER_CREATE_UNKNOWN_USER is set to
But that also shows that user existence is not checked against table
@daniel.pan, what do you think? Please also check my previous message, as they are related.