OAuth/SAPI application deployment failures in SNSC where the integration fails with an SSL/TLS error.

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

This article provides a solution for OAuth/SAPI application deployment failures in SNSC.

The integration fails with an SSL/TLS error while executing  configuration-checker script  failing to get token.

[INFO] Get token from OAuth-Server

GetToken : Get token failed. The remote server returned an error: (400) Bad Request..Exeception

Environment

• Automic Automation Engine 24.4.2 on Windows Server
• Apache Tomcat 9
• SNSC / OAuth-Server Integration 24.4.0

Cause

The error curl: (60) SSL certificate problem: self-signed certificate in certificate chain occurs because the curl.exe binary in use is an OpenSSL-linked build. Unlike the Windows-native curl (which uses Schannel and automatically checks the Windows Certificate Store), the OpenSSL-linked build maintains its own independent trust anchor and cannot verify the self-signed certificate chain automatically.

Resolution

Provided  the updated checker script which now supports both http/https - This will be included in 24.4.6 -TBA

To resolve this, you must explicitly point curl to the certificate using the --cacert parameter.

1. Locate your xuc4pass.ini configuration file (typically in the Automation Engine bin directory).
2. Export the OAuth server certificate in PEM format.
3. Update the cmd= line in xuc4pass.ini to include the --cacert parameter. Example: cmd=C:\cURL\bin\curl.exe --cacert "C:\Automic\certificates\oauth-server.pem" --user admin:password %0 --data "access_token=%1"
4. Save the configuration and execute the updated checker script  to verify that the connection succeeds.