Health Monitoring REST API – SSL Request Fails with "Connection or Outbound is Closed" Error in Postman.
Article ID: 404067
Updated On:
Products
Issue/Introduction
While attempting to request an authentication token from the Health Monitoring REST API using Postman, the request fails with the error message: "Connection or outbound is closed." This issue occurs specifically when sending the request over HTTPS (SSL). However, when the same request is sent over HTTP, it completes successfully.
Environment
Symantec Strong Authentication version: 9.1.5.1
Symantec Risk Authentication version: 9.1.5.1
Application Weblogic version: 14.1.1
Postman for Windows Version 5.5.0
Cause
The issue occurred because a wildcard certificate was used instead of a certificate containing the server's Fully Qualified Domain Name (FQDN), leading to SSL handshake failures. Additionally, the restapi.properties file was not properly updated with the correct configuration details, which further contributed to the connection error.
Resolution
To resolve the issue, update the restapi.properties and healthcheck.properties files with the correct configuration details required for secure communication. Ensure that the properties include accurate hostnames, ports, and SSL settings as needed by your environment.
Additionally, when sending HTTPS requests via Postman, use a certificate that includes the Fully Qualified Domain Name (FQDN) of the server. This ensures proper SSL handshake and prevents connection failures related to hostname mismatches. After making these changes, restart the application server (tomcat/ weblogic/ Jboss) to apply the updated configurations.
Additional Information
The following command can be used to verify the SSL/TLS connection and retrieve certificate details from the server:
Replace <hostname> with the actual server's fully qualified domain name (FQDN) or IP address.
This command helps identify issues such as certificate mismatches, expired certificates, or SSL handshake failures.
Feedback
