-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple accounts same username #44
Comments
Okay, I found what happens when you install in a subdomain. For some reason, when you login using YNH SSO, it will create an user in the database that's Haven't really find a way to circumvent this. Until it's fixed, if you install in a subdomain, your users will always be like that. For the admin account thing, I simply went to If that doesn't help, run the Now if you wanna log on on any sync client, you have to use I hope that helps. |
I know this issue, but for now I didn't find a clean way to fix this. It's related to this #5 And yes when I implemented the sso authentication growed... I tried to force to use a user instead of email it's just bad because in the seahub code where are everywhere a check that the username contains a Maybe the last solution is if seafile get a other domain for the email we dynamically force to use |
That's what I thought. Maybe you wanna add something about this in the README so more people are aware on how to handle the whole subdomain issue when installing? |
The problem is not specific to the subdomain. The problem could happen anytime when you have multiple domain on your instance... |
Well, thought about a solution improve this situation. I thought that we could maybe add a patch in seahub (which is written in python). But the problem is that the user validation (linked to LDAP) is in the ccnet part, which is written in c. So it's quite complicated to fix this.
I saw that I've already written something about that here. |
I started to investigate, the problem is in the SSO and LDAP check. What currently happen
What should be
|
This might be really complicated because the LDAP part of seafile is the ccnet and it's written in C.
Seeing your patch #46 it's possible |
I installed it in my instance on
seafile.example.com
and when I accessed it directly, it asked for my credentails, so I just input[email protected]
and it logged it fine.What I noticed a few hours later is that if I access the Seafile server using the yunohost SSO, it creates a different user library, even though the user is the same.
So, my login on Yunohost is
mail
. If I go toexample.com
and login withmail
and then click in Seafile, it will redirect to one library. If I go toseafile.example.com
and login with[email protected]
it creates another different library.I think this issue is somewhat related to #5 and #42
I also noted that in none of the cases I was able to use the admin interface, even though I set up
mail
as the admin user.Just ran a few tests and found out that:
example.com/seafile
directly, it won't redirect me to a SSL connection by itself. I might have to manually configure this in nginxThat's about it for now.
The text was updated successfully, but these errors were encountered: