Hi all, We are having a web app deployment issue possibly due to the new opensaml orbit bundle (because of having two opensaml versions). So until we find a proper solution we are downgrading the opensaml version back to 2.4.1.
Thanks, Maduranga. On Wed, Oct 7, 2015 at 11:09 AM, Hasintha Indrajee <hasin...@wso2.com> wrote: > STS functionality has been broken due to the upgrade of the opensaml > version (from 2.4.1 to 2.6.4) in carbon-identity. Error [1], can be > observed while invoking sts service with UT policy engaged. Further the > issue seems to be a failure to find class org.opensaml,XML from one of the > classes which resides in opensaml itself (org.opensaml.SAMLNameIdentifier). > > [1] <?xml version='1.0' encoding='utf-8'?><soapenv:Envelope xmlns:soapenv=" > http://schemas.xmlsoap.org/soap/envelope/";><soapenv:Header xmlns:wsa=" > http://www.w3.org/2005/08/addressing";><wsse:Security xmlns:wsse=" > http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"; > soapenv:mustUnderstand="1"><wsu:Timestamp xmlns:wsu=" > http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"; > wsu:Id="Timestamp-136"><wsu:Created>2015-10-06T11:47:27.145Z</wsu:Created><wsu:Expires>2015-10-06T11:52:27.145Z</wsu:Expires></wsu:Timestamp></wsse:Security><wsa:Action> > http://www.w3.org/2005/08/addressing/soap/fault</wsa:Action><wsa:RelatesTo>uuid:29736852-243e-40cb-9860-68d2db234e6f</wsa:RelatesTo></soapenv:Header><soapenv:Body><soapenv:Fault><faultcode>soapenv:Server</faultcode><faultstring>java.lang.NoClassDefFoundError: > Could not initialize class > org.opensaml.XML</faultstring><detail/></soapenv:Fault></soapenv:Body></soapenv:Envelope> > -- > Hasintha Indrajee > Software Engineer > WSO2, Inc. > Mobile:+94 771892453 > > -- Maduranga Siriwardena Software Engineer WSO2 Inc. email: madura...@wso2.com mobile: +94718990591
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
