In SAS® Viya® 3.4, the sas.identities.providers.ldap configuration instance might be missing from the services listing of identities services in SAS® Environment Manager.
When you encounter this problem, you see an error similar to the following in the identities service log:
ERROR 4142 --- [ bootstrap-8] c.s.c.bootstrap.ConfigurationLoader : service [df066bfeb7386955] [CONFIGURATION_BOOTSTRAP_HTTP_EXCEPTION_DETAILS] /configuration/configurations encountered an org.springframework.web.client.HttpClientErrorException attempting to POST to the REST end point
{"errorCode":0,"message":"BadRequestException: The media type \"application/vnd.sas.configuration.config.sas.identities.providers.ldap+json;version=1\" was not found. Http Status: 400\n","details":["correlator: 9039d153-0102-4076-abcc-0ac0a28c8c2e;09a516ed-2435-4b0e-9cd5-3b26c6ae9946","traceId: 22dfdc14d5e77651","path: /configuration/configurations"],"links":[],"version":2,"httpStatusCode":400}{5}
This error is benign, and you can ignore it. The sas.identities.providers.ldap configuration uses a set of default values.
To avoid getting the error in the identities service log and/or to make changes to the default values of properties defined in the service configuration definition, you must create a new configuration instance.
Complete these steps to create a new configuration instance:
- Open the Configuration page in SAS Environment Manager.
- Select Definitions in the drop-down list beside View.
- Select sas.identities.providers.ldap from the Definitions listing. No configuration is listed on the right side of the Configuration page.
- Click the New Configuration button. A new window titled "New sas.identities.providers.ldap Configuration" opens. The properties are pre-filled with default values.
- Replace any of the default values in this window as needed.
- Click Save to save this new configuration instance.
Refer to the "Configuration Properties: Reference (Services)" section in SAS® Viya® 3.4 Administration for more information about configuration definitions.
This problem is fixed in SAS® Viya® 3.5.