[MAGNOLIA-2047] NoSuchElementException in MgnlUserManager Created: 06/Feb/08 Updated: 23/Jan/13 Resolved: 03/Sep/08 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | security |
| Affects Version/s: | 3.5.3 |
| Fix Version/s: | 3.6.2, 3.6.3 |
| Type: | Bug | Priority: | Blocker |
| Reporter: | Sameer Charles | Assignee: | Jan Haderka |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| 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)
|
| Bug DoR: |
[ ]*
Steps to reproduce, expected, and actual results filled
[ ]*
Affected version filled
|
| Date of First Response: |
| Description |
|
This happens if
Exception on login, 16:25:51,990 ERROR [[default]] Servlet.service() for servlet default threw exception |
| Comments |
| Comment by Jan Haderka [ 03/Sep/08 ] |
|
exception is caused by the fact that user name is not present in PrincipalSet. We will treat this same way as when Subject is not present, so from Magnolia point of view this is not authenticated user. You can use such setup to authenticate to different systems, but to authenticate to Magnolia you need to provide valid user name. |