Application start fails due to a bean conflict (GONRG-4340)
Type of change
-
Bug Fix -
Feature
Does this introduce a change in the core logic?
- [NO]
Does this introduce a change in the cloud provider implementation, if so which cloud?
-
AWS -
Azure -
GCP -
IBM
Does this introduce a breaking change?
- [NO]
What is the current behavior?
Application start fails when SERVICE_TOKEN_PROVIDER is OPENID because of the OpenIdProviderConfigurationProperties beans conflict.
What is done?
Changed a name of OpenIdProviderConfigurationProperties bean to EntitlementsOpenIdProviderConfigurationProperties in entitlements service.
Have you added/updated Unit Tests and Integration Tests?
yes