[MGNLSSO-58] Magnolia didn't start correctly with the module. Created: 25/May/21 Updated: 26/May/21 Resolved: 26/May/21 |
|
| Status: | Closed |
| Project: | Single Sign On |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Neutral |
| Reporter: | Alberto Cordero | Assignee: | Maxime Michel |
| Resolution: | Not an issue | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
| 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 |
|
Using a clean installation of Magnolia 6.2.8 and SSO-Module V1.1 it's impossible to launch Magnolia using a correct configuration(decoration is not loaded). There is no way to login in Magnolia if you have the module installed. I have tried the decoration proposed in the docu page: https://docs.magnolia-cms.com/product-docs/Modules/List-of-modules/SSO-module.html#_yaml_configuration with my own Google Open ID/Azure parameters and it doesn't work, the decoration is not loaded by default. Steps to reproduce:
|
| Comments |
| Comment by Maxime Michel [ 26/May/21 ] |
|
I don't understand the issue completely. As said, the following:
Is by design. You can launch Magnolia and then work on finding out the exact values iteratively. We believe it's better to have the configuration in plain text rather than in JCR. You then say:
Maybe you are running into a corner case here and we can make the documentation clearer. Did you create the YAML decorator after the instance was started? I tend to do it before. It's possible that depending on your environment or whether Magnolia is in development mode, you may need to restart the instance. Did you try that? And for this:
We are looking at Google compatibility specifically in MGNLSSO-57. |
| Comment by Alberto Cordero [ 26/May/21 ] |
|
The problem jaas.config. Now, config is loaded. Not an issue. |