Dynamic reconfig of discovery endpoint not updating endpoints in all cases #16994
Labels
bug
This bug is not present in a released version of Open Liberty
release bug
This bug is present in a released version of Open Liberty
release:21008
team:Security SSO
If Social client is reconfigured in the following steps, it will not set the authorization, token, ... endpoints.
discoveryEndpointUrl
attribute and none of the discoverable config attributes setdiscoveryEndpointUrl
value with ""CWWKS5500E: A required configuration parameter authorizationEndpoint is missing or has an invalid value null
discoveryEndpointUrl
value with the original good discovery endpoint.CWWKS5500E: A required configuration parameter authorizationEndpoint is missing or has an invalid value null
CWWKS5500E: A required configuration parameter authorizationEndpoint is missing or has an invalid value null
It looks like the initial config sets up the discoveryDocumentHash which is used to populate the config.
The second config finds that the discovery endpoint is not set, so, it skips using the discoveryDocumentHash and tries to init the config from the values found in server.xml.
The hash instance is still set to the values from the first config.
The third config comes along and runs discovery. If then compares the current discoveryDocumentHash to the still existing discoveryDocumentHash - they're the same, so, it skips setting the values into the config object.
We need to do one of two things:
The text was updated successfully, but these errors were encountered: