YunoHost-Apps/seafile_ynh
1
0
Fork 0
mirror of https://github.com/YunoHost-Apps/seafile_ynh.git synced 2024-09-03 20:26:01 +02:00
Code Issues Projects Releases Packages Wiki Activity Actions

Add more info about email for user

Browse source
This commit is contained in:
Josué Tille 2019-07-30 22:51:02 +02:00
parent ecc8aae39d
commit cd742bb46d
No known key found for this signature in database
GPG key ID: 716A6C99B04194EF
1 changed files with 3 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

5
README.md
View file

@ -47,10 +47,12 @@ YunoHost specific features
This app support LDAP and the SSO authentification.
The restriction is that the user ID in this app is an email adress. So it's potentially possible to have multiple user account with the same username. By example you can have `john@yunohost.org` and `john@seafile.org`. You can see the issue [#5](https://github.com/YunoHost-Apps/seafile_ynh/issues/5) wich describe this problem. You can check that you are not in this case if by going in seafile admin page in the user tab can see all account.
The restriction is that the user ID in this app is an email address. So it's potentially possible to have multiple user account with the same username. By example you can have `john@yunohost.org` and `john@seafile.org`. You can see the issue [#5](https://github.com/YunoHost-Apps/seafile_ynh/issues/5) wich describe this problem. You can check that you are not in this case if by going in seafile admin page in the user tab can see all account.
The best configuration is to give to each user an email which contains the domain used by seafile.
**To fix this issue seahub don't allow any authentication from a user different than "username@seafile_domain.tld".**
### Supported architectures
Since seafile 6.3 the i386 architecture is no more supported.
@ -156,4 +158,3 @@ TODO
----
- Find a way to fix the issue https://github.com/YunoHost-Apps/seafile_ynh/issues/5