-
-
Notifications
You must be signed in to change notification settings - Fork 4.7k
Check expiry enforcement for all share types #40933
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
bbc12c4 to
8ef3748
Compare
8ef3748 to
3f51b16
Compare
come-nc
left a comment
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.
Enforcing now works for all three kind of shares.
But default seems broken for remote share it’s not applied?
2eda6db to
5840ca5
Compare
|
Hum, forced default expiration date now works for all cases, but for default value it uses the normal share default value for all 3 cases, even email and remote share, which should use their own default. |
1fd800a to
420c0d9
Compare
|
I had to run «npm run build» to fix the admin UI, so something is fishy in the commited dist. You will have to rebase on master and rebuild anyway. Also, there is a problem:
Please test thoroughly requesting for review again. |
come-nc
left a comment
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.
Enforcing is not working correctly (enforcing email enforces for local share, did not test other combinations)
Sorry @come-nc it appears, a merge conflict resolution overwrote some of the updates, during a rebase. |
About the It is now clear that this variable was poorly named. If we have |
420c0d9 to
e07d8e8
Compare
come-nc
left a comment
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.
🥳
e07d8e8 to
d6ff703
Compare
d6ff703 to
4548fdb
Compare
4548fdb to
a212ea9
Compare
|
/compile amend / |
We should check that a maximum expiry date has been enforced for all shares and NOT JUST FOR internal shares before enforcing a UI max date, like in commit 9757e68 Signed-off-by: fenn-cs <[email protected]>
Current expiration date errorneously assumes that `defaultExpirationDate` applies to all kinds of shares. But it only really applies to public shares despite its name. This commit, fixes that by paring expiration dates with the correct share types during new share initialization and simplifying the `hasExpirationDate` (check) property. Signed-off-by: fenn-cs <[email protected]>
a212ea9 to
2ca8561
Compare
|
/compile amend / |
2ca8561 to
eb0c923
Compare
eb0c923 to
2ca8561
Compare
|
/compile amend / |
`isDefaultExpireDateEnforced` and its corresponding `defaultExpirationDate` is currently treated as the enforcement fallback when share type enforcements are not set. However, `isDefaultExpireDateEnforced` and `defaultExpirationDate` are actually more like `isDefaultPublicExpireDateEnforced` and `defaultPublicExpirationDate` and therefore only applies to public shares. It might be ideal to rename this variables all the way from the backend config to the way we use them in the frontend code. Signed-off-by: fenn-cs <[email protected]> Signed-off-by: nextcloud-command <[email protected]>
2ca8561 to
8dfcf2e
Compare
|
Can we please backport this to stable27? |
|
Looks like this is already on stable27? At least when I cherry pick it is empty. cc @fenn-cs |
|
@marcelklehr it has commits from both pr's. |
We should check that a maximum expiry date has been enforced for all shares and NOT JUST FOR internal shares before enforcing a UI max date, like in commit 9757e68
Resolves : no issue