Authentication failure while invoking a SOAP call in AMX BPM from BusinessWorks.

Authentication failure while invoking a SOAP call in AMX BPM from BusinessWorks.

book

Article ID: KB0075859

calendar_today

Updated On:

Products Versions
TIBCO ActiveMatrix BusinessWorks 5.x
Not Applicable -

Description

Description:

The call to bpm api from BW 5.x fails with the error, "Authentication failed.

com.tibco.governance.pa.action.security.SecurityException: Signature verification failed. Message is not signed."
The same code works fine when tested from the BW Designer.

BPMNode.log

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

[ERROR] [amx.bpm.app] com.tibco.amx.governance.pa.action.wss.VerifyAuthenticationAction - TIBCO-OGS_PA-901713: Authentication failed.

[ERROR] com.tibco.amx.login.failure - TIBCO-OGS_PA-901402: Authentication failed.

[ERROR] com.tibco.governance.amxagent.msginterceptor.api.impl.AMXMessageInterceptorImpl - Policy enforcement in the Pipeline failed.
                com.tibco.governance.pa.action.security.SecurityException: Authentication Failed.

[ERROR] [amx.bpm.app] com.tibco.amx.governance.agent.action.api.AbstractActionManager - Failed to execute action

                com.tibco.governance.pa.action.security.SecurityException: Authentication Failed.

[INFO ] [amx.bpm.app] com.tibco.amx.governance.pa.pdp.PolicyDecisionPointImpl - TIBCO-OGS-GA-900515: A security exception was encountered while enforcing an action. Exception: com.tibco.governance.pa.action.security.SecurityException: Authentication Failed.

[ERROR] [amx.bpm.app] com.tibco.amx.governance.pa.action.wss.VerifyAuthenticationAction - TIBCO-OGS_PA-901713: Authentication failed.

[ERROR] [amx.bpm.app] com.tibco.amx.governance.agent.action.api.AbstractActionManager - Failed to execute action.

                com.tibco.governance.pa.action.security.SecurityException: Authentication Failed.

[INFO ] [amx.bpm.app] com.tibco.amx.governance.pa.pdp.PolicyDecisionPointImpl - TIBCO-OGS-GA-900515: A security exception was encountered while enforcing an action. Exception: com.tibco.governance.pa.action.security.SecurityException: Authentication Failed.

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
 

BPM.log

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

[ERROR] com.tibco.amx.login.failure - TIBCO-OGS_PA-901402: Authentication failed.

[ERROR] com.tibco.governance.amxagent.msginterceptor.api.impl.AMXMessageInterceptorImpl - Policy enforcement in the Pipeline failed.

                com.tibco.governance.pa.action.security.SecurityException: Authentication Failed

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

 

BW log

>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

<MsgCode>SOAPPLUGIN-100023</MsgCode>

<Data>

<defaultFaultElement>

<faultcode>SOAP-ENV:Server</faultcode>

<faultstring>Authentication Failed.</faultstring>

<faultactor>DefaultRole</faultactor>

</defaultFaultElement>

</Data>

<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

Issue/Introduction

Authentication failure while invoking a SOAP call in AMX BPM from BusinessWorks.

Resolution

If the issue happens after deployment but the same project works fine in Designer, it normally indicates that needed security policy to authenticate to the AMX BPM API  is not added in the EAR. Adding the security policies and rebuilding the EAR may resolves the issue.

And if the issue is seen while testing in Designer, it could be caused by:

1. The Security Policy is not associated to SOAP Request Reply Activity
or
2. Credentials in the  Security Policy  are incorrect 

Please double check the Security Policy, Policy Association as well as the Credentials. It is also very practical to try with the same credentials from another tool such as SOAP UI or Curl to see if the invoke is successful.