[MGNLSSO-23] Only run SSO authentication on selected paths Created: 09/Jun/20 Updated: 03/Oct/23 Resolved: 17/Jun/20 |
|
| Status: | Closed |
| Project: | Single Sign On |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.0 |
| Type: | Task | Priority: | Neutral |
| Reporter: | Maxime Michel | Assignee: | Maxime Michel |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Template: |
|
||||||||
| Acceptance criteria: |
Empty
|
||||||||
| Task DoR: |
Empty
|
||||||||
| Date of First Response: | |||||||||
| Epic Link: | Magnolia SSO w/ pac4j | ||||||||
| Description |
|
— This ticket's initial intent was to make pac4j copy Magnolia's security in the 99% of URLs where pac4j doesn't need to be in front of Magnolia. However, only enabling pac4j on desired target URLs such as Admincentral solves the problem with a better approach, and less code on top of that. |
| Comments |
| Comment by Espen Jervidalo [ 11/Jun/20 ] |
|
Here's a similar issue related to the liveness and readiness module. |
| Comment by Espen Jervidalo [ 11/Jun/20 ] |
| Comment by Maxime Michel [ 12/Jun/20 ] |
|
Much easier than doing this would be to enable pac4j solely for Admincentral, no? |