we’re using Seafile Pro with LDAP authentication. All users, who have the ldap attribute service=seafile set, can use the service. This is configured as an ldap filter in ccnet.conf.
Now I found out, that a user who configured the seafile client (6.1.8) under Windows, can still connect to the seafile server, even if I the service attribute in ldap is deleted. Logging in to the web interface directly is forbidden, but calling the website from the seafile client still works!!! It seems, that the seafile client doesn’t make a new authentication even after rebooting the windows pc. How is that possible??? That means, that we cannot forbid users to use seafile as long as they use the seafile client.