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
Unable to save a Workflow Approval Email Template that contains non-Latin characters in RSA Identity Governance & Lifecycle 52Number of Views Using RSA SecurID Software Token 5.0 for Windows with Citrix non-persistent Xenapp virtual desktops 209Number of Views Utilize Authentication Manager SDK 8.0 in non-weblogic environment 179Number of Views AFX Server installs on Windows in a non-functional state due to JAVA_HOME in RSA Governance & Lifecycle 23Number of Views How to make the sender address field non-editable when clicking on send email button while performing the review in RSA Id… 25Number of Views
Trending Articles
RSA Authentication Manager Upgrade Process How to Update the Root (Server) and Client Certificates in RSA Identity Governance & Lifecycle RSA Authenticator 6.2.2 for Windows Administrator Guide RSA SecurID software token .sdtid file fails to import into RSA SecurID Software Token 5.0 for Windows RSA MFA Agent 2.3.6 for Microsoft Windows Installation and Administration Guide
Don't see what you're looking for?