SAP connector fails with hostname not found when using a non-default port in RSA Identity Governance & Lifecycle
Originally Published: 2019-09-20
Article Number
Applies To
RSA Version/Condition: All
Issue
GetHostByName: '10.100.99.99:3301' not found SYSTEM CALL getaddrinfo
The Connection Details used in this example are:
A test connection using the default SAP port of 3300 is successful:
Cause
In the example above, RSA Identity Governance & Lifecycle is converting the entire string 10.100.99.99:3301 as a Hostname to an IP address.
Resolution
/H/hostname/S/port
For example,
Related Articles
What Ports are used by enVision 195Number of Views Incorrect passcode under certain conditions from CA Siteminder to RSA Authentication Manager 8.x 61Number of Views Unable to save a Workflow Approval Email Template that contains non-Latin characters in RSA Identity Governance & Lifecycle 52Number of Views Utilize Authentication Manager SDK 8.0 in non-weblogic environment 180Number of Views How to close ports used by the RSA Authentication Agent to block SSLv3 communication to RSA Authentication Manager 8.x 399Number of Views
Trending Articles
RSA Authentication Manager 8.9 Setup and Configuration Guide How to 'Trust' the RSA Authentication Manager Security Console Self-Signed Root CA certificate and prevent Cert warnings. RSA Authentication Manager 8.9 Release Notes (January 2026) Configure RSA Authentication Manager as a Secure Proxy Server for Cloud Access Service RSA Authentication Manager Upgrade Process
Don't see what you're looking for?