Error: Sm_AgentApi_IsProtectedEx, Sm_AgentApi_LoginEx in Web Agent log

Products

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

Issue/Introduction

 

When running a Web Agent, the below errors can be seen in the Web Agent log :

  [ERROR] LLA: SiteMinder Agent Api function failed -'Sm_AgentApi_IsProtectedEx' returned '-1'.
  [ERROR] LLA: SiteMinder Agent Api function failed - 'Sm_AgentApi_LoginEx' returned '-2'.
  [ERROR] LLA: SiteMinder Agent Api function failed - 'Sm_AgentApi_LoginEx' returned '-1'.

 

Environment

 

Policy Server and Web Agent all versions;

 

Cause

 

Sm_AgentApi_LoginEx is a function call of Web Agent.

This function has -1 or -2 error code return:

  -1 means that Web Agent failed to communicate with the policy server;
  -2 means connection timeout;

'Sm_AgentApi_IsProtectedEx' is also a function call of Web Agent to check whether the accessed resource is protected or not.

Error code returned:

  -1 indicates that the Policy Server could not be reached;
  -2 indicated Policy Server connection is timeout;

These are quite generic error messages. These indicate that:

1.  Either the Policy Server was down;
       
    OR
   
   
2. Policy Server was not responding to the Web Agent due to being busy and lack of resources and as a result, the Web Aqgent request timeout occurs;
   
   OR
   
   
3. The Web Agent request is not reaching the Policy Server or the request is timing out, due to network latency;

Resolution

 

1. Verify if the corresponding policy server was too busy or lacking resources during these error timeframes and also check if there were any network issues, due to which the Agent could not communicate with the Policy Server and logged these errors (1).
2. Also to accommodate network latency, increase the value of the "AgentWaitTime" parameter in the WebAgent.conf file (2).
   
   

Additional Information

 

(1)

    Error: Agent Api function failed with Web Agent and Load balancer
    
    
(2)

    Accommodate Network Latency