[CNTCTSAPP-80] Reconfigure availability of de/activation and other actions Created: 30/May/14 Updated: 10/Jul/14 Resolved: 07/Jul/14 |
|
| Status: | Closed |
| Project: | Contacts App |
| Component/s: | None |
| Affects Version/s: | 1.0 |
| Fix Version/s: | 1.2.2, 1.3.1 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Roman Kovařík | Assignee: | Eric Hechinger |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | quickwin, support | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoD: |
[ ]*
Doc/release notes changes? Comment present?
[ ]*
Downstream builds green?
[ ]*
Solution information and context easily available?
[ ]*
Tests
[ ]*
FixVersion filled and not yet released
[ ] 
Architecture Decision Record (ADR)
|
| Date of First Response: | |
| Epic Link: | publishActionsAvailability |
| Description |
|
Since any de/activation request actually writes to involved node/s, to update theirs metadata, those actions should be implicitly allowed only for users having write permissions to them. Since |
| Comments |
| Comment by Eric Hechinger [ 02/Jul/14 ] |
|
add missing restrictions to the 1.3.1 and 1.2.2 |
| Comment by Philip Mundt [ 07/Jul/14 ] |
|
confirmDeleteFolder, confirmDeleteContact is still available for a user without proper rights. Triggering the action will result in javax.jcr.AccessDeniedException. |
| Comment by Eric Hechinger [ 07/Jul/14 ] |
|
only done under confirmDeleteContact as confirmDeleteFolder extends confirmDeleteContact |