Hello,
we have the problem that after the upgrade from 11.0.5 to 11.0.18, users who log in with SSO (Microsoft Azure OAUTH) no longer work (Seafile would create a new user).
We have checked the ccnet_db.EmailUser and seahub_db.social_auth_usersocialauth tables (the links look good). Where else can we check and are there any other issues during the upgrade that could play a role?
We are using Seafile Professional.
Thank you very much!
What record is created when the user login in ccnet_db.EmailUser and seahub_db.social_auth_usersocialauth? What is the old record in seahub_db.social_auth_usersocialauth for the same user?
Hello Daniel,
after the upgrade from 11.0.5 to 11.0.18 the tables look identical.
However, after a subsequent SSO login (Microsoft Entra), a new entry is created for an existing user (with a new GUID@auth.local). The only difference is that the value of the provider column is now microsoft.com and no longer login.microsoftonline.com as with the old entries.
If we change the value of the provider column of the original entry to microsoft.com, the login works without creating a new entry.
Is this the fix or is there a bug or configuration error?
Many thanks!
Matthias
I think the problem is very specific to your setup. So currently we will not consider it as a bug and look into it.