We are using WSO2 4.1.1 for user management. Is there a way to do a session time out in WSO2 4.1.1?
(I am looking if there is a fix for this in WSO2 4.1.1. Currently, I am not looking at migrating to WSO2 4.5
where this is mentioned as a supported feature).
I am referring to the following link where it says the WSO2 4.1.1.code has been changed to handle session time out.
https://wso2.org/jira/browse/IDENTITY-1030
Are these changes available as a new version of jar compatible with the WSO2 4.1.1 version?
Thanks in advance for the help
You won't be able to get a new version of the jar and use it with the WSO2 IS 4.1.1. AFAIK, IS 4.1.1 was never released, I think you are using a build shared via dev# list.
Anyway, you can try following.
Checkout the source for the corresponding jars in WSO2 IS 4.1.1. Try to checkout from branch. For example: https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.1.0/components/identity/org.wso2.carbon.identity.base/
Fix the issue and do 'mvn clean install'
Copy the target jar as a patch.
Run server with -DapplyPatches
In this way, you can try to fix this issue.
If we discover issues with any product after it has been released, you will be able to get the fix only in a newer version. Otherwise, you need to patch the existing jar versions.
I hope this helps.
Related
I would like to understand the hazelcast version being used with git release 5.11 https://github.com/wso2/product-is/releases/tag/v5.11.0
and where is it specified? Can I upgrade it to 4.2.4.wso2v1 to avoid the vulnerabilities?
Hazelcast is mainly used in the WSO2 carbon-kernel and simply upgrading 3.12.x to 4.2.x would result in issues as it is being a major version upgrade, there are set of API changes done from Hazelcast. This issue has tracked the effort of Hazelcast version upgrade on WSO2 products. You can port those fixes. Also note that WSO2 IS 6.0.0 has upgraded the Hazelcast.
I am getting log4j-core -> 2.12.0 vulnerability with org.wso2.carbon.identity.application.authentication.framework
As per the github link - https://github.com/wso2/product-is/blob/v5.11.0/pom.xml
the compatible version for WSO2 IS v5.11 is 5.18.187
But as I checked over maven also, the specified version https://mvnrepository.com/artifact/org.wso2.carbon.identity.framework/org.wso2.carbon.identity.application.authentication.framework/5.18.187
is log4j core vulnerabilities in compile dependency https://mvnrepository.com/artifact/org.wso2.carbon.identity.framework/org.wso2.carbon.identity.testutil/5.18.187
Could you please suggest, if I should go with upgrading the version of org.wso2.carbon.identity.application.authentication.framework or should just add direct dependency for log4j-core 2.17.2
Upgrading the org.wso2.carbon.identity.application.authentication.framework would not be compatible with the other modules in the distribution and I recommend not doing so since it could lead to some breaking changes in the product features.
And upgrading the log4j-core dependency in the org.wso2.carbon.identity.application.authentication.framework to the 2.17.2 version alone would not work since there are other artifacts that were affected by the log4j vulnerability.
Since this vulnerability was identified, WSO2 has released an updated version for the product-is which you can download from their website.
The Version 5.11.0 - SERVICE PACK 01 which you can download from here would have the updated product-is v5.11.0 with the fixes for the log4j vulnerability. And it also includes bug fixes for the initial 5.11.0 release.
Hence, I recommend going with the already existing 5.11.0 - SERVICE PACK 01
instead of manually updating the affected artifacts.
Upgrading org.wso2.carbon.identity.application.authentication.framework might lead in to breaking changes and updating log4j-core dependency will not resolve the issue since there can be other components whcih are also affected by this vulnerability.
WSO2 has already identified and fixed this. I would like to recommend you to download and use the latest Identity Server version (IS 6.0.0) from the official WSO2 website or from git releases. The WSO2 team has paid special attention to fixing most of the 3rd party vulnerabilities in this release and there are so many new features available.
Updated 1:
You can follow the temporary solution specified in this doc if you don't have a paid subscription or are unable to get the latest Identity Server product (NOTE that it is a temporary fix).
I'm trying to upgrade a wso2 install from 1.9.0 to 1.10.0 to support HTTP PATCH, however, the bug here: https://wso2.org/jira/browse/APIMANAGER-4504 has broken JWT generation. I see the bug is fixed in 1.10.1, but I cannot find any reference to this version in documentation or in the release downloads for wso2.
Is this version released? Is it available, or does it have to be build manually? If so, could you provide instructions on how to do this?
There isn't any release with 1.10.1 version, next released version is API Manager 2.0.
You can find the components here: https://github.com/wso2/carbon-apimgt/tree/v6.0.4
Produce distribution here: https://github.com/wso2/product-apim/tree/v2.0.0
I have installed DSS feature on ESB. While deploying DSS artifact, I came across error similar to one below
WARN - DefaultAppDeployer Can't deploy artifact : EmployeeDataService of type : service/dataservice. Required features are not installed in the system
The wso2 jira indicates that the issue has been resolved
https://wso2.org/jira/browse/CARBON-15657
How do I incorporate this fix in my wso2 esb 4.9 installation?
You can get relevant patches for that fixes and apply to your version. As most of patches are provided upon customer requests, it is better to use release versions which are having those fixes.
In ESB 5.0.0, all fixes are attached and it may be release within this month (July, 2016).
I'm running WSO2 ESB 4.0.3 and noticed 4.5 came out. I've tried searching but haven't been able to find anything regarding how to upgrade to the new version without breaking files I've changed. Anyone have any ideas or direct me to a document on how I can do this?
Thanks,
Jared
Unfortunately there is no "upgrade" szenario available. We installed a fresh copy of ESB 4.5 and then copied our configurations from the following directories:
lib/log4j.properties
lib/core
repository/conf
repository/components/lib
repository/resources
repository/deployment/server/synapse-configs/default
But these were the directories where we know that we made customizations. If you don't know anymore your changes from the original 4.0.3, download a fresh copy and compare with your current implementation of the ESB.
Attention: The important axis2.xml has changed a bit in its structure - so copying the file as it is will not work. Just copy the changed configuration lines in it.
For ESB specifically you need to pay attention to the followings if you have made any changes.
passthru-http.properties
synapse.properties
nhttp.properties
which were available under lib/core/WEB-INF/classes needs to be moved to repository/conf