[MGNLSSO-29] Bail out if the SSO realm not defined Created: 08/May/20 Updated: 07/Jul/20 Resolved: 14/May/20 |
|
| Status: | Closed |
| Project: | Single Sign On |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Neutral |
| Reporter: | Maxime Michel | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Template: |
|
| Acceptance criteria: |
Empty
|
| Task DoR: |
Empty
|
| Epic Link: | Magnolia SSO w/ pac4j |
| Description |
|
This is a common problem I see during development. The IDE will update Maven artifacts or I will forget to add the SSO realm into jaas.config, and I lose time. The module should warn when the realm isn't there, as nothing is going to work. Do it when the module starts. Halt Magnolia start if possible. |
| Comments |
| Comment by Maxime Michel [ 14/May/20 ] |
|
When jaas.config isn't setup properly, Magnolia needs to be restarted in order for the module to work. Noticing the problem while Magnolia is starting and bailing out early would be nice:
Also, I would really like to stop Magnolia, as I think that only issuing a log message will have little impact. But there is no clean API to do this, and this could become a nightmare in production. So in the end I have no good solution to the problem. Hopefully production will be less impacted than development (once the setup is right, it shouldn't move). If not, I can always revisit the problem at a later point. |