Symantec Access Management

I am trying to call a SOAP service using JAX WS from Siteminder custom authentication scheme.

The environment is using jdk 1.6.0.33.

The code works standalone from the host, however, when tried via Siteminder webagent-authentication scheme flow, it stops at initialization of Service.

The service is triggered from "authenticate" method of the authentication scheme. However, when control reaches that line of code, there is no exception caught and no error in the logs and the next line is "query" method of the authentication scheme being triggered.

Does Siteminder need any additional JAX-WS dependencies?

Can anyone else

Megha Saxena wrote:

 

I am trying to call a SOAP service using JAX WS from Siteminder custom authentication scheme.

The environment is using jdk 1.6.0.33.

The code works standalone from the host, however, when tried via Siteminder webagent-authentication scheme flow, it stops at initialization of Service.

 

The service is triggered from "authenticate" method of the authentication scheme. However, when control reaches that line of code, there is no exception caught and no error in the logs and the next line is "query" method of the authentication scheme being triggered.

 

Does Siteminder need any additional JAX-WS dependencies?

help with this question?

Thank you!

Megha MeghaSaxena4211797

Am not a big developer, but thinking logically in lines of the sequences of action performed.

Initialization of Authentication scheme occurs once the IsProtected Call is made to Policy Server. There is a lot of activity that needs to happen post a initialization.

Are we sure that post initialization of Authentication scheme; the response is passed to WebAgent. The WebAgent collects the credentials and sends it to Policy Server. Now the Authentication is invoked again to verify the credentials.

My question would be are we sure the Authentication Scheme has collected the credentials (This would be first check point).

Regards

Hubert