|
| Getting Invalid SAML token error while trying to access wls9.2 |
 |
Thu, 22 Nov 2007 01:30:19 -080 |
Hi,
I am using wss4j at the client side as SAML token issuer to add saml assertion
to the soap envelop whose target is a webservice deployed in a aqua logic
service bus 2.6. But at the server side i.e wls9.2, i am getting following
exception
weblogic.xml.crypto.wss.SecurityTokenValidateResult@326f6a[status: false][msg
The SAML token is not
valid.]</faultstring></soapenv:Fault></soapenv:Body></soape
nv:Envelope>
weblogic.xml.crypto.wss.WSSecurityException: Security token failed to validate.
weblogic.xml.crypto.wss.SecurityTokenValidateResult@326f6a[status: false][msg
The SAML token is not valid.]
at
weblogic.xml.crypto.wss.SecurityImpl.unmarshalAndProcessSecurityToken(SecurityIm
pl.java:476)
at weblogic.xml.crypto.wss.SecurityImpl.unmarshal(SecurityImpl.java:392)
This error seems to be coming during unmarshalling of soap envelop which is run
before request goes to SAML Identity Assertion provider V1. Certificates are
properly configured at both client and server side so it seems that generated
SAML assertion is not compliant with weblogic 9.2 unmarshalling process.
Has anyone got any solution for this problem. I am not exactly looking for full
SSO configuration at the weblogic side so I have not set any credential mapper
(which is also a saml issuer). Nor have i done any setting related with SSO on
weblogic.
Any idea will really be helpful in this regard.
|
| Post Reply
|
|
|
|
|
|
|
|
|
|