Symantec Access Management

Hi

We developed one application using Agent API. Agent API is used to authenticate user. We deployed the application in Weblogic server and it is working fine. But it is not working as expected in JBOSS 6.4 . Is there any restriction for using agent API with JBOSS?

Hi,

Can you provide more information on how the agent API not working in JBOss? Are you getting any error return?

Do you have JBoss agent on the JBoss application server?

Regards,

Kar Meng

We developed on webapplication and deployed in JBOSS. We dont have  JOBSS agent.

Hi,

There are no known restrictions with using the Agent API inside of JBoss.  Suggest you open a support case and have the issue investigated.

Regards,

Sandy Green

Is it the initialization errors ?

Yes Ujwol.

So what are the actual errors on the agent side?

Was it able to handshake with PS? Did you verify PS side of logs?

Also, did you apply JCE patch ? This is the most common cause for initialisation errors.

Ujwol the system is not available for some days for development. I will give the details once it is available. Thank you for the help

Hi rahulk.s

In JBoss 6.4, when startup the JBoss server (via standalone or domain), it should printed out the Java that JBoss use

ie:

JAVA: "C:\Program Files\Java\jdk1.7.0_79\bin\java"

In above example, the JCE patch need apply to C:\Program Files\Java\jdk1.7.0_79\jre\lib\security. Two files (US_export_policy.jar, local_policy.jar) need to be replaced.

On policy server side, did you find handshake error?

ie:

[ERROR][sm-Tunnel-00010] Bad security handshake attempt. Handshake error: 3152]

[ERROR][sm-Tunnel-00030] Handshake error: Failed to receive client hello. Socket error 0]

if it is, most probably the agent unable to communicate with PS and causing the initialization error. JCE patch is common that cause the problem.

Regards,

Kar Meng