[MAGNOLIA-6097] GroupManager API should provide removeGroup() and removeRole() methods Created: 23/Feb/15 Updated: 02/Jul/15 Resolved: 11/May/15 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | security |
| Affects Version/s: | 5.3.7 |
| Fix Version/s: | 5.4 |
| Type: | Improvement | Priority: | Neutral |
| Reporter: | Richard Gange | Assignee: | Trang Truong |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | support | ||
| Remaining Estimate: | 0d | ||
| Time Spent: | 1.5d | ||
| Original Estimate: | 3h | ||
| Attachments: |
|
||||
| Issue Links: |
|
||||
| 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: | |||||
| Description |
|
Add removeGroup() and removeRole() methods |
| Comments |
| Comment by Aleksandr Pchelintcev [ 11/May/15 ] |
|
1. Instead of returning null in case of exception - an IllegalArgumentException should be thrown. |
| Comment by Federico Grilli [ 12/May/15 ] |
|
I agree with Sasha about not breaking binary compatibility in a maintenance release. Asked support if we can postpone to 5.4 |