-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Extra documentation for smb update notification with user provided auth #652
Conversation
Using login credentials is only supported with 'Login credentials, save in database'. | ||
|
||
When using 'Login credentials, save in database' or 'User entered, stored in database' authentication the notify process | ||
is not able to read the smb credentials from the storage configuration, in those cases you can provide |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This sentence is the opposite of the paragraph before it. Could you check it again?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it's correct, although it might look a bit conflicting.
The notify command can't use the '... save in database' credentials because it is not running in the context of a user.
The file scanner can use the credentials because it is run within a user context so it knows which set of credentials to pick
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Then write it like that and describe what the difference between notify command and file scanner is ;)
@icewind1991 Could you refine the sentence to make it a bit more clear? Thanks |
126f8b5
to
7946be1
Compare
Cleared it up a bit |
stable12 32241b6 |
Document the limitations to update notifications as described in nextcloud/server#3524