| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| WS-Security using policy sets & policy set bindings |
« View previous topic :: View next topic » |
| Author |
Message
|
| PEPERO |
 Posted: Sat Jun 15, 2013 7:19 pm Post subject: WS-Security using policy sets & policy set bindings |
 |
|
Disciple
Joined: 30 May 2011
Posts: 177
|
Hi;
I've defined a policy set and policy set binding using the WMB explorer. I've designed and implemented a web service provider flow using soapinput/soapreply nodes. When trying to deploy the bar file for which the defined policy set and policy set binding are set as the provider, the following exception is thrown :
| Code: |
+BIP3728E BROKER1 default 38 CONFIGURATION OF WS-SECURITY LAYER USING POL
060
ICY SET 'Default_Policy_Set' AND POLICY SET BINDING 'Default_Bindings'
FAILED. : ImbSOAPJniManager(780)
+BIP3727E BROKER1 default 38 com.ibm.wsspi.wssecurity.core.SoapSecurityEx
061
ception: CWWSS5434E: Missing classname attribute com.ibm.ws.wssecurity
.confimpl.PrivateCommonConfig$CallbackHandlerConfImpl(className= null
, keyStore= null , keyInformation= null , trustAnyCertificate= false ,
provider= null , pkixBuilderParams= null , userId= null , userPasswor
d= XXXXXXXX , properties= ) in CallbackHandler. : ImbSOAPJniManager
(780)
+BIP3701E BROKER1 default 38 A JAVA EXCEPTION WAS THROWN WHILST CALLING T
062
HE JAVA JNI METHOD 'Axis2NodeRegistrationUtil_registerInputNode'. THE
JAVA EXCEPTION WAS 'BIP3726E: com.ibm.broker.axis2.MbSoapException: Fa
iled to setup Axis2'. THE JAVA STACK TRACE WAS 'Frame : 0 com.ibm.brok
er.axis2.MbSoapException: Failed to setup Axis2| @: com.ibm.broker.axi
s2.Axis2NodeRegistered$SOAPConfig.<init>(Axis2NodeRegistered.java:301)
| @: com.ibm.broker.axis2.Axis2NodeRegistered.<init>(Axis2NodeRegister
ed.java:132)| @: com.ibm.broker.axis2.Axis2EngineManager.registerNode(
Axis2EngineManager.java:81)| @: com.ibm.broker.axis2.Axis2NodeRegistra
tionUtil.registerInputNode(Axis2NodeRegistrationUtil.java:153)|Frame :
BIP2154I BROKER1 default 38 EXECUTION GROUP FINISHED WITH CONFIGURATION
ESSAGE. : ImbConfigurationNode(458)
|
Following the CWWSS5434E says that "CallbackHandler classname attribute is required.Verify the binding if the CallbackHandler className is valid."
What does the callbackhandler in this case stands for? Where should i set the related classname properties. I've double checked the defined truststore and keystore (and the storepass/keypass passwords) defined for the "default" execution group introduced to the broker "broker1".
I've tested the client keystore and truststore ; generated in the same way that i've done for the "default" execution group stores; using the SOAPUI and every thing was ok.
Does anyone has any idea about how to resolve this exception? |
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Mon Jun 17, 2013 3:19 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
|
| Back to top |
|
|
| PEPERO |
| Posted: Mon Jun 17, 2013 7:36 am Post subject: |
|
|
Disciple
Joined: 30 May 2011
Posts: 177
|
Thanks for your recommandation.
When checking the Compatibility mode with in the Bindings first page , the problem would be resolved, seems that it has to be told to support only X509 token types. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
