-
-
Couldn't load subscription status.
- Fork 4.6k
fix(files_sharing): use user defined passwords #55026
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
Conversation
A previous MR(54055) resulted in the NcActionInput component responsible for creating file shares discarding user provided passwords, in favor of the system generated one. This was caused by drift between the component and the underlying Share model, resulting in the component calling .sync on a non-existent attribute, which meant the password was never updated. To reproduce (with password_policy enabled): * Under a files "External Shares", click "Create public link" * Supply a password to the password field, e.g., "testing-password_123" * Click "Create share" * Attempt to navigate to the generated share link and access the shared file with the password you provided at the time of creating the share. * The provided password will be rejected, as it was never updated from the system generated one. Signed-off-by: Darian Culver <darian.culver@catalyst.net.nz>
|
/compile |
|
Possible performance regression detected Show Output |
|
/backport e4b7d65 to stable31 |
|
/backport e4b7d65 to stable32 |
|
/backport e4b7d65 to stable30 |
Signed-off-by: nextcloud-command <nextcloud-command@users.noreply.github.com>
|
Possible performance regression detected Show Output |
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.
Can you add a cypress test for it? Just to ensure that it does not break again in the future.
|
I think this is fixed by #55081 already |
Copy of #54399
Summary
A previous MR(#54055) resulted in the NcActionInput component responsible for creating file shares discarding user provided passwords, in favor of the system generated one.
This was caused by drift between the component and the underlying Share model, resulting in the component calling .sync on a non-existent attribute, which meant the password was never updated.
To reproduce (with password_policy enabled):
TODO
N/A
Checklist