search cancel

Unable to connect to Policy Server. Please check agent name and shared secret

book

Article ID: 252895

calendar_today

Updated On:

Products

SITEMINDER CA Single Sign On Agents (SiteMinder)

Issue/Introduction

An Agent is crashing during startup and producing the following error.

[com.xyz.test.security.impl.gss2.AuthenticationServiceImpl.checkSessionValidity(AuthenticationServiceImpl.java:820)
2022-10-19 18:43:41,800 ERROR [AuthenticationServiceImpl]: 124200
Unexpected Eception: Unable to connect to Policy Server. Please check agent name and shared secret
Unable to connect to Policy Server. Please check agent name and shared secret user id [a1234]]
java.lang.RuntimeException: Unable to connect to Policy Server. Please check agent name and shared secret ...
 

Environment

Release : 12.8.05

Cause

Misconfiguration at the Custom Java Agent.
It is not sending the correct AgentName+SharedSecret when contacting Policy Server.

Resolution

[com.xyz.test.security.impl.gss2.AuthenticationServiceImpl.checkSessionValidity(AuthenticationServiceImpl.java:820)
2022-10-19 18:43:41,800 ERROR [AuthenticationServiceImpl]: 124200
Unexpected Eception: Unable to connect to Policy Server. Please check agent name and shared secret
Unable to connect to Policy Server. Please check agent name and shared secret user id [a1234]]
java.lang.RuntimeException: Unable to connect to Policy Server. Please check agent name and shared secret ...

 

"com.xyz.test.security....." suggest this is custom code developed by customer.

Basically what is happening is... this problematic agent is configured to use 4.x agent type which would have "sharedsecret" configured in the agent.

The custom java agent that is trying to communicate with policy server will send the "AgentName" and its "SharedSecret".

Both information must match for this agent to communicate with the Policy Server but it did not match.

As a result, "Unable to connect to Policy Server. Please check agent name and shared secret ..."

 

Customer must ensure they use the correct agentname and the sharedsecret in their custom java agent.