Unable to resolve the fully qualified host name. Exiting with HTTP 500 server error '00-0016'

Products

• CA Single Sign On Secure Proxy Server (SiteMinder)
• CA Single Sign On SOA Security Manager (SiteMinder)
• CA Single Sign-On

Issue/Introduction

Observed below error in the WebAgent.log file:

[CSmHttpPlugin.cpp:406][ERROR][sm-HTTPAgent-00030] Unable to resolve fully qualified host name. Exiting with HTTP 500 server error '00-0016'.
[CSmResourceManager.cpp:158][WARNING][sm-AgentFramework-00480] HLA: Missing resource data. 

Also observed following error message in the WebAgenttrace.log:

[CSmHttpPlugin.cpp:399][CSmHttpPlugin::ProcessResource][][][][][][][Resolved HTTP_HOST: '10.0.0.1'.]
[CSmHttpPlugin.cpp:5518][Entered CSmHttpPlugin::ResolveFQServerName sHost: ][][][][][][][10.0.0.1]
[CSmHttpPlugin.cpp:5600][CSmHttpPlugin::ResolveFQServerName: isIP][][][][][][][10.0.0.1]
[CSmHttpPlugin.cpp:10195][CSmHttpPlugin::DoDNSLookup ][][][][][][][Entered Function server: 10.0.0.1, port: ]
[CSmHttpPlugin.cpp:10264][CSmHttpPlugin::DoDNSLookup Error: ][][][][][][][Name or service not known]
[CSmHttpPlugin.cpp:10280][CSmHttpPlugin::DoDNSLookup ][][][][][][][Leaving Function]
[CSmResourceManager.cpp:94][CSmResourceManager::ProcessResource][][][][][][][SM_WAF_HTTP_PLUGIN->ProcessResource returned SmExit.]
[CSmResourceManager.cpp:160][CSmResourceManager::ProcessResource][][][][][][][Plugins did not collect required resource data.] 

 

Environment

Component: Web Agent - All Supported Versions.

Cause

The 00-0016 error is being reported because a request is being made using IP Address instead of the FQDN, and the Agent is unable to resolve the IP to a FQDN.

Resolution

Please use the FQHN instead of an IP address.

SiteMinder uses the SMSESSION cookie to manage user sessions and for single sign-on purposes, this cookie needs to be set with a domain.

If the initial request must use an IP address, the administrator can set "ForceFQHost=Yes" in the Web Agent ACO.

Set ForceFQHost = yes (default: no)

The ForceFQHost parameter uses Reverse DNS Lookup to resolve a FQHN and redirect to that resolved address.

This will only work if the reverse DNS lookup is configured correctly.

If a load balancer or proxy acts as the frontend, please work with its vendor to ensure the FQHN is passed in the HTTP Host header to the backend web server integrated with the web agent.

Additional Information

- Document reference:

SiteMinder Browser Cookies