Hi Malithi, I have observed the same issue by only updating carbon-registry from 4.4.8 to 4.4.9. So I believe this happens due to dependency changes occurring when doing that.
Thank You! On Wed, Mar 30, 2016 at 11:36 PM, Malithi Edirisinghe <malit...@wso2.com> wrote: > Hi All, > > We have upgraded opensaml version from 2.4.1 to 2.6.4 in carbon-identity > 5.0.8. In order to build the product with this opensaml upgrade we had to > update carbon deployment version from 4.5.3 to 4.6.1 to avoid wiring to > opensaml older version. > > Along with this upgrade we had to upgrade below too. > carbon-kernel 4.4.3 to 4.4.5 > carbon-commons 4.4.8 to 4.5.2 > carbon-registry 4.4.8 to 4.5.2 > carbon-multitenancy 4.5.0 to 4.5.1 > carbon-business-process 4.4.4 to 4.4.7 > carbon-analytics-common 1.0.0 to 5.0.8 > axiom 1.2.11.wso2v6 to 1.2.11.wso2v10 > rampart 1.6.1.wso2v16 to 1.6.1.wso2v19 > jaggerjs 0.12.2 to 0.12.3 > > However, after this upgrade adding workflows fail, since the client cannot > authenticate to the BPELUploader service via mutual ssl. > This occurs as the client module fails to communicate the client > certificate. > But when I tried the same service for mutual ssl via soap ui and via a > third party client I wrote which uses the same stub packed, it worked. > > Highly appreciate any help. > > Thanks, > Malithi > > -- > > *Malithi Edirisinghe* > Senior Software Engineer > WSO2 Inc. > > Mobile : +94 (0) 718176807 > malit...@wso2.com > -- *Chamila Dilshan Wijayarathna,* Software Engineer Mobile:(+94)788193620 WSO2 Inc., http://wso2.com/
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
