[MGNLSSO-314]  SSO Module 3.1.x breaks SSO-Connector configuration via ENV vars Created: 09/Oct/23  Updated: 10/Oct/23  Resolved: 10/Oct/23

Status: Closed
Project: Single Sign On
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Medium
Reporter: Marcel Hodan Assignee: Unassigned
Resolution: Not an issue Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: PNG File image-2023-10-09-12-27-43-734.png     PNG File image-2023-10-09-12-32-48-531.png     PNG File image-2023-10-09-12-35-15-362.png     PNG File image-2023-10-09-12-44-31-110.png    
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   

Steps to reproduce

  1. increase magnolia version from 6.2.37 to >= 6.2.38
  2. use info.magnolia.connector.sso:magnolia-sso-connector: 2.7.4
  3. define sso information in property (like before)
  4. set information via environment variables
  5. Configuration in JCR

Expected results

  • Client Secret configured inĀ info.magnolia.connector.sso.oic.settings.OICSettings

    Actual results

  • No client secret is configured

    Workaround

    Development notes



 Comments   
Comment by Marcel Hodan [ 09/Oct/23 ]

Problem also occured in 6.2.37 (after cleaning workspace).
Can be closed until further notice.

Comment by Richard Gange [ 10/Oct/23 ]

Hello marcel.hodan-

If you are a customer or partner please request a support account by emailing info@magnolia-cms.com.

BR
Rich

Generated at Mon Feb 12 10:53:06 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.