[MGNLSSO-270] Custom authorizationGenerators configuration not found Created: 21/Apr/23  Updated: 18/Jun/23  Resolved: 25/May/23

Status: Closed
Project: Single Sign On
Component/s: None
Affects Version/s: 3.1.3
Fix Version/s: saas, 3.1.4

Type: Bug Priority: Neutral
Reporter: Richard Gange Assignee: Nguyen Phung Chi
Resolution: Fixed Votes: 0
Labels: None
Σ Remaining Estimate: Not Specified Remaining Estimate: Not Specified
Σ Time Spent: 12d 2.5h Time Spent: 12d 2.5h
Σ Original Estimate: Not Specified Original Estimate: Not Specified

Attachments: PNG File empty-array-1.png     PNG File empty-array-2.png     PNG File login-works.png    
Issue Links:
Relates
relates to MGNLSSO-287 Able to not defining any authorizatio... Open
relation
Sub-Tasks:
Key
Summary
Type
Status
Assignee
MGNLSSO-278 Implementation Technical task Completed Mikaël Geljić  
MGNLSSO-279 Review Technical task Completed Evzen Fochr  
MGNLSSO-280 PiQA Technical task Completed Nguyen Phung Chi  
MGNLSSO-281 Final QA Technical task Closed Nguyen Phung Chi  
Template:
Acceptance criteria:
Empty
Task DoD:
[X]* Doc/release notes changes? Comment present?
[X]* Downstream builds green?
[X]* Solution information and context easily available?
[X]* Tests
[X]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Epic Link: SSO maintenance
Sprint: AdminX 35, AdminX 36
Story Points: 5
Team: AdminX
Work Started:
Approved:
Yes

 Description   

Customer reports that upon startup the custom authorizationGenerators configuration is not being found. Subsequent restart of the system fixes the problem.

As you can see in the two pictures of the logs, the field "authorizationGenerators" is filled with an empty array.
Example 1

Example 2

After restarting the instance and logging in again the custom authorizationGenerator is in the field --> login works.

Reproduce
Steps are unknown in an exact form. Customer has followed all instructions mentioned here. Configuration/code has been checked by support and dev team.

Actual
Sometimes the configuration is being picked up and sometimes not.

Expected
Configuration should always be picked. If the array is empty that should trigger some warning/error in the log. The authorizationGenerator should be a mandatory configuration.

Notes
There seems to be an issue with reading the configuration from the external light module.


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