| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| SAML Identity propagation |
« View previous topic :: View next topic » |
| Author |
Message
|
| fenway_frank |
 Posted: Thu Jan 05, 2012 3:25 pm Post subject: SAML Identity propagation |
 |
|
Apprentice
Joined: 21 Oct 2011
Posts: 43
Location: Boston, MA USA
|
Hi, My SOAPInput message flow app (wmb 7.0.0.3) needs to participate in WS-Trust exchange to validate an inbound SAML token (the token is created by the consumer app and passed to this msg flow in ws-security header). The internal STS endpoint supports WS-Trust 1.3 and SAML 2.0 basic profile. Followed InfoCenter instructions and created SecurityProfile that enables identity propagation and also created policy set/bindings that specify SAML 2.0 "pass thru" authn token. Attached the profile and policy set/bindings to the SOAPInput node in my message flow but no luck. Immediately fails with attached exception. Any ideas?
| Code: |
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body>
<soapenv:Fault xmlns:axis2ns1="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
<faultcode>axis2ns1:FailedAuthentication</faultcode>
<faultstring>CWWSS6521E: The Login failed because of an exception: javax.security.auth.login.LoginException: caught exception from broker</faultstring>
<detail>
<Exception>org.apache.axis2.AxisFault: CWWSS6521E: The Login failed because of an exception: javax.security.auth.login.LoginException: caught exception from broker
at org.apache.axis2.AxisFault.makeFault(AxisFault.java:430)
at com.ibm.ws.wssecurity.handler.WSSecurityConsumerBase.invoke(WSSecurityConsumerBase.java:132)
at com.ibm.ws.wssecurity.handler.WSSecurityConsumerHandler._invoke(WSSecurityConsumerHandler.java:518)
at com.ibm.ws.wssecurity.handler.WSSecurityConsumerHandler.invoke(WSSecurityConsumerHandler.java:221)
at org.apache.axis2.engine.Phase.invoke(Phase.java:318)
at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:268)
at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:175)
at com.ibm.broker.axis2.Axis2Invoker.processInboundRequest(Axis2Invoker.java:2937)
at com.ibm.broker.axis2.Axis2Invoker.invokeAxis2(Axis2Invoker.java:2607)
at com.ibm.broker.axis2.TomcatNodeRegistrationUtil.invokeAXIS2(TomcatNodeRegistrationUtil.java:470)
Caused by: com.ibm.wsspi.wssecurity.core.SoapSecurityException: CWWSS6521E: The Login failed because of an exception: javax.security.auth.login.LoginException: caught exception from broker
at com.ibm.wsspi.wssecurity.core.SoapSecurityException.format(SoapSecurityException.java:136)
at com.ibm.ws.wssecurity.wssapi.token.impl.CommonTokenConsumer.getSoapSecurityException(CommonTokenConsumer.java:642)
at com.ibm.ws.wssecurity.wssapi.token.impl.CommonTokenConsumer.invoke(CommonTokenConsumer.java:537)
at com.ibm.ws.wssecurity.core.WSSConsumer.callTokenConsumer(WSSConsumer.java:2412)
at com.ibm.ws.wssecurity.core.WSSConsumer.callTokenConsumer(WSSConsumer.java:2233)
at com.ibm.ws.wssecurity.core.WSSConsumer.invoke(WSSConsumer.java:919)
at com.ibm.ws.wssecurity.handler.WSSecurityConsumerBase.invoke(WSSecurityConsumerBase.java:111)
... 8 more</Exception>
</detail>
</soapenv:Fault>
</soapenv:Body>
</soapenv:Envelope> |
|
|
| Back to top |
|
 |
| lancelotlinc |
| Posted: Fri Jan 06, 2012 5:40 am Post subject: |
|
|
Jedi Knight
Joined: 22 Mar 2010
Posts: 4941
Location: Bloomington, IL USA
|
Looks like the code post you posted is a Soap fault message from some Web Service. Is it the fault message from your WMB flow ? Please post the relevant syslog messages that go along with it.
_________________
http://leanpub.com/IIB_Tips_and_Tricks
Save $20: Coupon Code: MQSERIES_READER |
|
| Back to top |
|
|
| fenway_frank |
| Posted: Fri Jan 06, 2012 7:04 am Post subject: |
|
|
Apprentice
Joined: 21 Oct 2011
Posts: 43
Location: Boston, MA USA
|
yes, the fault message was a reply from the wmb flow captured by soapUI. it appears my problem is cert related. this came from windows event log (note, i intentially removed cert org unit and org information):
MB7BROKER.CDS_ONLINE01
'connect'
'javax.net.ssl.SSLHandshakeException: com.ibm.jsse2.util.g: PKIX path building failed: java.security.cert.CertPathBuilderException: PKIXCertPathBuilderImpl could not build a valid CertPath.; internal cause is: java.security.cert.CertPathValidatorException: The certificate issued by OU=, O=, C=US is not trusted; internal cause is: java.security.cert.CertPathValidatorException: Certificate chaining error' |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Fri Jan 06, 2012 7:33 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| fenway_frank wrote: |
yes, the fault message was a reply from the wmb flow captured by soapUI. it appears my problem is cert related. this came from windows event log (note, i intentially removed cert org unit and org information):
| Code: |
MB7BROKER.CDS_ONLINE01
'connect'
'javax.net.ssl.SSLHandshakeException: com.ibm.jsse2.util.g: PKIX path building failed: java.security.cert.CertPathBuilderException: PKIXCertPathBuilderImpl could not build a valid CertPath.; internal cause is: java.security.cert.CertPathValidatorException: The certificate issued by OU=, O=, C=US is not trusted; internal cause is: java.security.cert.CertPathValidatorException: Certificate chaining error' |
|
Check for a missing intermediate certificate in your truststore... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
| fenway_frank |
| Posted: Fri Jan 06, 2012 2:38 pm Post subject: |
|
|
Apprentice
Joined: 21 Oct 2011
Posts: 43
Location: Boston, MA USA
|
ok, beyond the cert problem but now belive i have a bigger, more fundamental roadblock...
i don't think broker supports endpoints that adopt MEX standard. we use ping federate version 6.5 as our internal sts implementation which is a fully compliant SAML MEX endpoint. the mex standard includes ws-trust 1.3 wsdl, however, that wsdl does not define any bindings. bottom line, i cannot use soaprequest node to hit the sts using ws-trust wsdl. i need to communicate with sts to validate an inbound saml token.
has anyone encountered similar problem? if so, how did you configure policy set/bindings, security profile, and the soap request node? |
|
| 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
|
|
|
|
