[MAGNOLIA-5137] Jaas chain to use is only configurable when using FormLogin Created: 25/Jun/13 Updated: 04/Mar/19 |
|
| Status: | Open |
| Project: | Magnolia |
| Component/s: | core, security |
| Affects Version/s: | None |
| Fix Version/s: | 4.5.x |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Magnolia International | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| Template: |
|
| Patch included: |
Yes
|
| 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
|
| Description |
|
For some reason, when using info.magnolia.cms.security.auth.login.FormLogin, one can configure which JAAS chain to use (which can be useful with multiple webapps running in the same container, when they need different configurations). It seems like it should simple to fix, but that leaves me dumbfounded as to why this was this way in the first place. Please investigate before applying patch. |