We have a stack of WSO2 servers where Identity server 5.1. works with API Manager as key manager. These servers work in a production environment.
Now a new version of API Manager (2.0) have appeard and I found out in documentation that WSO2IS 5.1 isn't compatible to work as key manager with new API manager.
My question is:
It would be better:
To wait for a new IS version (5.2) and then to upgrade together API Manager and IS
or
To upgrade API manager now and to switch functions of key manager from UIS to new API Manager and later install new IS version.
I think the first way is better because of changes in UM and AM databases for new API Manager. Now AM and UM databases are common for 2 servers.
Am I right?
I recommending to wait until Identity Server 5.2.0 released, also you can get the latest Identity Server 5.2.0-SNAPSHOT release here. We are hoping to release IS 5.2.0 by mid of September.
Related
I am trying to utilise multitenancy feature in WSO2 by using github releases(https://github.com/wso2/product-is/releases/tag/v5.11.0). I just wanted to understand if there are any limitations for the same between enterprise version downloaded from wso2 site and github releases.
Thanks
WSO2 doesn't have an Enterprise Version of the product. Everybody uses the same base release and if you have a subscription you will be receiving product updates for bug fixes, improvements, security issues etc. Other than that there are no hidden features or limitations in the Opensource version.(Rarely some features are introduced as updates, in these cases you may not receive them) The subscription is for getting updates and getting support from WSO2.
You can read more about WSO2 subscription from here.
Adding to #YCR answer, yes, multi tenancy is supported in IS 5.11.0 and IS 6.0.0 and it was supported throughout IS 5.x series. Please see Tenant Management on WSO2 documentation.
I am trying to install following feature in wso2 API manager 2.0.
http://xacmlinfo.org/2015/05/13/federated-authenticators-in-wso2-api-manager-wso2apim/
but I am getting error in API manager's console while installations.
It seems the above package is not compatible for 2.0 version.
Please suggest me the exact version of 'Application Authenticator' feature which is compatible with wso2 AM version 2.0.
Thanks in advance
It seems the p2 repos are still not updated with the latest Authenticator versions based on Identity Application Management Server Feature 5.2.0 or above. This will be updated soon with the next release.
However you can use WSO2 IS for this use case. You can configure SSO for APIM with IS using this link . Then you can federate IS for OpenAM with this link . With that you can connect APIM with openAM.
Hope this helps.
We recently pushed through the upgrades of our WSO2 instances to IS 5.1, API 1.10.0 and GREG 5.1. We are a clustered setup, with IS 5.1 serving as Key Manager, API 1.10.0 serving as the API Gateway, and GREG 5.1 serving as the API Store/Publisher, all using the a shared MGT DB.
Once the upgrades completed we started noticing errors such referencing "IAT.CONSUMER_KEY".
ERROR {org.wso2.carbon.apimgt.impl.dao.ApiMgtDAO} - Failed to get keys for application: 35 {org.wso2.carbon.apimgt.impl.dao.ApiMgtDAO}
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown column 'IAT.CONSUMER_KEY' in 'where clause'
Looking into the jar we noticed that the API Store/Publisher jar was still referencing the old column name, CONSUMER_KEY, for IDN_OAUTH2_ACCESS_TOKEN. In a shared setup the IS 5.1 upgrade dropped that column and created the column CONSUMER_KEY_ID.
I installed a vanilla 5.1 Greg and installed the 2.0.1 Store plugin again and the jar impacted definitely appears to be trying to use CONSUMER_KEY:
org.wso2.carbon.apimgt.impl_2.0.1.jar
Anyone hit this issue? Did we outpace the API Store/Publisher plugin for GREG? Or, I have just setup the system incorrectly.
Thanks for the help,
Kevin
You need to install API key manager features or use pre-packaged WSO2 Identity Server 5.1.0 as [1] when configuring IS 5.1.0 as key manager with APIM 1.10.0.
https://docs.wso2.com/display/CLUSTER44x/Configuring+the+Identity+Server+5.1.0+as+a+Key+Manager+with+API+Manager+1.10.0
I'm trying out the beta/unreleased code for EMM 2.0 (which I believe is now MDM) and I undestand that the mobile app store and publisher function have been moved to Enterprise Store, however I'm unable to see/add mobile apps - I only see Gadgets and Sites.
I was looking for the source in case I missed the plugin, but at https://github.com/wso2/carbon-store/tree/master/features/extensions I only see Gadgets and Sites.
Can someone tell me how to enable mobile apps and/or point me to the mobile app plugin source?
FYI, I installed ES from http://wso2.com/products/enterprise-store/ and also master branch from the following:
https://github.com/wso2/product-mdm.git
https://github.com/wso2/carbon-device-mgt-plugins.git
https://github.com/wso2/carbon-device-mgt.git
You can use WSO2 App Manager,
Please read this doc to integrate it with WSO2 EMM
https://docs.wso2.com/display/APPM100/Mobile+Apps+Configurations
WSO2 is working on integrating app management features with WSO2 EMM 2.0.0. Device and App Management both features will be shipped with EMM 2.0.0 once it is released.
I'm considering using the functions of WSO2 IS. However, I already have WSO2 ESB deployed in a production environment, so I'd prefer to add IS features to the already existent ESB environment.
I was able to start with the IS 4.1.0 bundle, add the Carbon 4.0.5 P2 repository (ESB 4.6.0 is built upon that version of Carbon) and install ESB 4.6.0 features, but I cannot seem to be able to do the opposite, since as far as I can tell WSO2 IS is based on Carbon 4.0.6, but there's no P2 repo for it.
What's the proper way to install IS features into ESB, if any?
I haven't tried installing 4.0.7 Identity Server features to ESB 4.0.6. But I can advice you to not to do it. Reason is: Identity Server 4.1.0 has some changes done to the user management core bundles which are not compatible with the older releases. Therefore, you can try to install an older version of identity server features on top of ESB 4.6.0. Identity Server 4.0.0 was released with Carbon 4.0.3. So, I think you should try with Carbon 4.0.3 p2 repository to install identity features on ESB 4.6.0.
Please use 4.0.7 P2 repository for new IS features which IS 4.1.0 based on.
http://dist.wso2.org/p2/carbon/releases/4.0.7/