[MGNLSSO-208] Check effective/parsed configuration via debug logs Created: 29/Nov/22 Updated: 16/Feb/23 |
|
| Status: | Open |
| Project: | Single Sign On |
| Component/s: | None |
| Affects Version/s: | 3.0.0 |
| Fix Version/s: | None |
| Type: | Story | Priority: | Neutral |
| Reporter: | Mikaël Geljić | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| 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)
|
||||||||
| Epic Link: | SSO maintenance | ||||||||
| Team: | |||||||||
| Description |
|
As an admin, I want to check effective/parsed configuration via debug logs, so that I can (re)validate my configuration is being correctly applied by Magnolia, before trying to log in and see. This would be useful when working with YAML config, especially on 6.2 setups with the YAML bridge config. Finding the right config can be an error prone exercise, due to indentation mishaps, possibly amplified by config refactorings we did in 3.0.0, e.g. moving authorization-generators, which admins also have to move, with a chance of accidentally breaking indentation or some other syntax. Note: we may do this before or after |