Hi, While testing out the latest IS pack I noticed the $subject. It hangs after printing environment properties from CarbonCoreActivator. After debugging in OSGi console mode I noticed that rampart-core_1.6.1.wso2v15 and rampart-trust_1.6.1.wso2v15 dependency bundles are in INSTALLED state which is blocking some of the core identity bundles from going to ACTIVE state.
Running the diagnose OSGi command on ramport-core gave me the following; reference:file:../plugins/rampart-core_1.6.1.wso2v15.jar [377] Package uses conflict: Import-Package: org.apache.ws.security; version="[1.5.11.wso2v9,2.0.0)" Package uses conflict: Import-Package: org.apache.ws.security.components.crypto; version="[1.5.11.wso2v9,2.0.0)" Package uses conflict: Import-Package: org.apache.ws.security.handler; version="[1.5.11.wso2v9,2.0.0)" Package uses conflict: Import-Package: org.apache.ws.security.message; version="[1.5.11.wso2v9,2.0.0)" Package uses conflict: Import-Package: org.apache.ws.security.message.token; version="[1.5.11.wso2v9,2.0.0)" Package uses conflict: Import-Package: org.apache.ws.security.saml; version="[1.5.11.wso2v9,2.0.0)" Package uses conflict: Import-Package: org.apache.ws.security.util; version="[1.5.11.wso2v9,2.0.0)" Looks like wss4j dependency version has been upgraded with this commit [1] to 1.5.11.wso2v11 but rampart v1.6.1-wso2v15 release is still referring to wss4j 1.5.11.wso2v9 [2]. Appreciate if IS team can look into this. [1] https://github.com/wso2/carbon-identity/commit/7f2e8271ed5d3e82606f33334be1b991c82a621e [2] https://github.com/wso2/wso2-rampart/blob/v1.6.1-wso2v15/pom.xml#L558 Thanks. -- Akila Ravihansa Perera WSO2 Inc.; http://wso2.com/ Blog: http://ravihansa3000.blogspot.com
_______________________________________________ Dev mailing list Dev@wso2.org http://wso2.org/cgi-bin/mailman/listinfo/dev
