[MAGNOLIA-1174] wrong login gives 401 instead of Magnolia page with error message Created: 30/Oct/06 Updated: 23/Jan/13 Resolved: 10/Oct/07 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | None |
| Affects Version/s: | 3.0 RC3 |
| Fix Version/s: | 3.0 RC4, 3.5 RC1 |
| Type: | Bug | Priority: | Trivial |
| Reporter: | Anne-Marie Scheidegger | Assignee: | Philipp Bärfuss |
| 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 |
|
In 3.0 RC2 and before |
| Comments |
| Comment by Philipp Bracher [ 17/Nov/06 ] |
|
the page is showing up again, but we should add a messages to tell the user that the login failed |
| Comment by Sameer Charles [ 18/Jan/07 ] |
|
we can display different messages, its trivial but every user will have different requirements in any case we will add a simple message saying "invalid user or password". Please note that if authentication fails it always send UNAUTHORIZED header 401 to the client, so you can configure your own error handler for the application |
| Comment by Magnolia International [ 10/Oct/07 ] |
|
The support for different login error messages has been implemented for 3.1 |