SAP connector fails with hostname not found when using a non-default port in RSA Identity Governance & Lifecycle
Originally Published: 2019-09-20
Last Modified: 2023-11-30
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
Intermittent IWA Authentication Issues for IDR Portal Users 12Number of Views Utilize Authentication Manager SDK 8.0 in non-weblogic environment 182Number of Views Using RSA SecurID Software Token 5.0 for Windows with Citrix non-persistent Xenapp virtual desktops 215Number of Views How to fix PeopleSoft connectors that are in a non-deployed state after installing RSA Via Lifecycle and Governance (L&G) … 44Number of Views SA server is not connecting SA Live cloud due to Local network Proxy 8Number of Views
Trending Articles
Don't see what you're looking for?