Arctera

API call to add additional trusted certificates fails when REST API server is configured with third-party CA certificate (4056593)

The REST API server is configured with a third-party CA certificate when the VCS resource attribute ThirdPartyCA is set to a non-zero value. The API call to add additional trusted certificates is POST /infoscale/api/1.0/cacert.

If the REST API server is configured to use third-party CA certificates””rather than the Infoscale internal CA certificates””during the initial installation and configuration, a directory required for configuring additional certificates is not created. Consequently, the API fails when it attempts to create a combined certificate bundle. The failure is reported as a response with the status code 500.

The REST API logs include error messages of the type:

FileNotFoundError: [Errno 2] No such file or directory:
  '/var/VRTSvcs/vcsauth/data/VCSAUTHSERVER/root/.
  VRTSat/profile/certstore/cacert.pem'
<!--NeedCopy-->

Workaround: The required directories get created if you restart the REST API server after such an error has occurred. A restart is required only after the first time that this error occurs; the subsequent usage of the API succeeds.

In a default configuration, you can use VCS resource management commands to restart the REST API server. Use the following commands sequentially to take the RestSG service group offline and bring it back online.

# hagrp -offline RestSG -sys <system_name>

# hagrp -wait RestSG State OFFLINE -sys <system_name>

# hagrp -online RestSG -sys <system_name>

# hagrp -wait RestSG State ONLINE -sys <system_name>

API call to add additional trusted certificates fails when REST API server is configured with third-party CA certificate (4056593)

In this article