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
It appears notify_push takes it's UID from the foldername in the mount-directory it detects changes in and does not read the home column when the user is one from user_saml.
Background: The user_saml app has users with uid,displayname,home in the database, so you can set different files directory independent from their UIDs.
In my case, I use a numeric ID >100000 for a SAML user different from their human-readable UID. So user1 can have their files at /data/100001 for example. This allows unique identification via the numeric ID and the UID visible to others can be changed around without much hassle.
This seems to lead notify_push to look for a user of uid=100001 instead of searching the actual oc_user_saml_users table in the database for the corresponding home (and falling back to uid=$directoryname, as the column is usually empty).
The result of this is that users regularly (I guess when notify_push detects a filechange somewhere) get thrown out of their session and Nextcloud force-reloads the active window throwing users out of their email-drafts, opened documents, etc.
I think this is the relevant notify_push part where we see the discrepancy that its verifying credentials using the numerical IDs and otherwise talking to the users via their uid. Note that the numerical id in L2 (1000072) is not the corresponding id of the user in L4 ($UID).
As I am not capable of debugging this myself, can you confirm that notify_push does not check the home column for user_saml users? Or is it rather that you use the Nextcloud API instead of the database so this is something Nextcloud internal which does not check the home column?
If so, could this be added? :)
The text was updated successfully, but these errors were encountered:
It appears notify_push takes it's UID from the foldername in the mount-directory it detects changes in and does not read the
home
column when the user is one from user_saml.Background: The
user_saml
app has users withuid,displayname,home
in the database, so you can set different files directory independent from their UIDs.In my case, I use a numeric ID >100000 for a SAML user different from their human-readable UID. So user1 can have their files at /data/100001 for example. This allows unique identification via the numeric ID and the UID visible to others can be changed around without much hassle.
This seems to lead notify_push to look for a user of uid=100001 instead of searching the actual
oc_user_saml_users
table in the database for the corresponding home (and falling back to uid=$directoryname, as the column is usually empty).The result of this is that users regularly (I guess when notify_push detects a filechange somewhere) get thrown out of their session and Nextcloud force-reloads the active window throwing users out of their email-drafts, opened documents, etc.
I think this is the relevant notify_push part where we see the discrepancy that its verifying credentials using the numerical IDs and otherwise talking to the users via their uid. Note that the numerical id in L2 (1000072) is not the corresponding id of the user in L4 ($UID).
This is the nextcloud.log at that point:
As I am not capable of debugging this myself, can you confirm that notify_push does not check the
home
column for user_saml users? Or is it rather that you use the Nextcloud API instead of the database so this is something Nextcloud internal which does not check thehome
column?If so, could this be added? :)
The text was updated successfully, but these errors were encountered: