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
Using RSA SecurID Software Token 5.0 for Windows with Citrix non-persistent Xenapp virtual desktops 215Number of Views Utilize Authentication Manager SDK 8.0 in non-weblogic environment 182Number of Views Intermittent IWA Authentication Issues for IDR Portal Users 12Number of Views How to fix PeopleSoft connectors that are in a non-deployed state after installing RSA Via Lifecycle and Governance (L&G) … 47Number of Views SA server is not connecting SA Live cloud due to Local network Proxy 8Number of Views
Trending Articles
RSA Authentication Manager 8.9 Patches and Hotfixes Readme RSA MFA Agent 2.5 for Microsoft Windows Installation and Administration Guide RSA-2026-24: RSA Authentication Manager Security Update for Third-Party Component Vulnerabilities IDR SSO - Step 3: Deploy the Identity Router RSA Authentication Manager 8.9 Setup and Configuration Guide
Don't see what you're looking for?