You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm preparing to switch to NC 29 and the external user extention I previously used is not supported anymore, so I tried user_backend_sql_raw as a replacement.
It sounds very good, except that an issue with login sensitivity: if I log with a name like 'foo' or 'Foo', login will succeed, like this should, but then, the two logins will then have different homes, which is the issue.
With internal Nextcloud user login or other external authentication apps I experimented, case sensitivity never caused this issue.
Best regards,
Strato
The text was updated successfully, but these errors were encountered:
AVee
added a commit
to AVee/user_backend_sql_raw
that referenced
this issue
Sep 14, 2024
Extend the get_password_hash_for_user query to allow it to return the
uid as well. This makes it possible to support normalizing usernames,
using email as username and other types of mapping in the query.
Probably deals with PanCakeConnaisseur#56
Hi,
I'm preparing to switch to NC 29 and the external user extention I previously used is not supported anymore, so I tried user_backend_sql_raw as a replacement.
It sounds very good, except that an issue with login sensitivity: if I log with a name like 'foo' or 'Foo', login will succeed, like this should, but then, the two logins will then have different homes, which is the issue.
With internal Nextcloud user login or other external authentication apps I experimented, case sensitivity never caused this issue.
Best regards,
Strato
The text was updated successfully, but these errors were encountered: