[MAGNOLIA-1757] Better Exception handling in Group and Role manager Created: 05/Oct/07 Updated: 27/Nov/13 Resolved: 05/Sep/13 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | security |
| Affects Version/s: | 3.1 M3 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Minor |
| Reporter: | Sameer Charles | Assignee: | Roman Kovařík |
| Resolution: | Outdated | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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 |
|
When the group doesn't exist info.magnolia.cms.security.MgnlGroupManager.getGroup(String) and when the property of external user is null info.magnolia.cms.security.ExternalUser.getProperty(String) unnecessarily log this information. It makes problem example with ldap module. |
| Comments |
| Comment by Roman Kovařík [ 05/Sep/13 ] |
|
Related group and role managers changes: |