Till WSO2 version 5.11 we are using username as input parameter for many rest API's but in WSO2 version 6.0, we are using user-id as input parameter. Is there any documentation available for that, we are using user-id as input parameter?
AFAIK the user unique Ids were introduced from IS 5.10.0 onwards (what has changed). Since then almost all the API implementations were based on the unique id. You can find the API documentation here.
If there is any backward incompatible API when migrating from 5.11 to 6.0.0 better to mention it in the original issue.
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've published an API named as "DocumentAPI", after publishing I can find two API's with the name "DocumentAPI" in publisher. Can find only one API with name "DocumentAPI" in store. Tried deleting, recreating and republishing the API and also restarted my server.
Two gateways(internal(MZ) and external(DMZ)) are there in the current environment which means some the APIs are specific to internal and some are specific to external and some are published to both the gateways(cuurent problematic API is published to both the gateways)
There is no synchronize method setup between these two nodes.
We are on APIM-2.6.0
There is no duplicate entries in AM_API, REG_PATH tables with repect to problematic API. Only in publisher UI we are seeing two APIs with same name,version & conetxt and when I modify any one API the change immediately relfecting into other API as well. In store only one API it is showing and when I test this API through Postman subsequent calls are getting failed.
Note: Publishing in fully distributed environment.
Are you using APIM wum updated pack or vanilla pack? If it is wum, what is the wum level(AM_HOME/updates/wum)?
Did you try to recreate a new API instead of that "DocumentAPI" name (with a different name) and did you see the same issue for this when publishing to both GW nodes?
In APIM 2.6.0 we have seen a similar issue if we have created an API with uppercase (eg: AbcAPi) and published it. Then remove it and try to recreate the api with the same name but lowercase (eg: abcApi) and publish it. Then we can see two API in the publisher portal but not in Store UI. And AM Table has one record. But in the registry has two paths (as you have seen).
eg:
/_system/governance/apimgt/applicationdata/provider/admin/AbcAPi
/_system/governance/apimgt/applicationdata/provider/admin/abcApi
One path for that old api name and another path for the new API. Since currently, we have fixed this, and that fix is available in the latest wum updated pack of the APIM 2.6.0. Therefore did you notice such differences in both reg paths (select * from REG_PATH where REG_PATH_VALUE).
If yes, it has fixed in the latest wum of APIM 2.6.0. The reason here is when removing API, it remains some metadata of old API and when recreating registry keep both paths.
When creating an API in wso2 APIM, it doesn't allow to create two APIs with the same name, context and version (name, context and version should unique).
As per the provided mentioned details, we hope that both APIs in the publisher node has the same name, context and version.
In your distributed set up how many GWs are available(one or many)?
If has multiple GW nodes, are you using any deployment artefact syncronize method like NFS?
What is the APIM version
Are you noticing two records for the above API in the AM database(AM_API table)?
We recently upgraded WSO2 IS from 5.3 to 5.5. As per the WSO2 IS documentation, it says "From 5.4.0 onwards, the functionality provided by these SOAP APIs are provided through REST APIs. We recommend using REST APIs instead."
But i could not find the rest URLs for calling the AdminServices .
Hereis the URL that i am referring to:
https://docs.wso2.com/display/IS550/SOAP+APIs
Can anyone help me in finding out the rest APIs for the SOAP services - "RemoteUserStoreManagerService" and "UserIdentityManagementAdminService" please?
Documentation you have pointed seems be little bit misleading.
The topic "Calling Admin Services" does not explain about a particular API. Instead it explains how to invoke a SOAP service in the Identity Server in general.
Next, each of the topic in the list does not have a exactly matching REST endpoints. For an example RemoteUserStoreManagerService SOAP API can be used for user management operations. For this you can use SCIM 2.0 REST APIs.
Can you explain the use case you are trying to achieve with UserIdentityManagementAdminService, so that I can help you with finding the correct REST endpoint for it.
There are certain API rate limits applied on Facebook v2.7 onwards. Is there anyway I can revert back to v2.6?
You can't use a deprecated API. There is no way you can use API v2.6 now.
The only possible way would be to get an old app that was created using API v2.6.
No you can't use an older version. You have to use the latest version.
You can find this on the facebook for developers website
An app can make calls to the version of the API that was the latest
available when the app was created, as well as any newer,
un-deprecated versions launched after the app is created.
As an example, if your app was created after v2.0 was released, it
will be able to make calls to v2.0 until the expiration date of that
version, and any subsequent versions (v2.1 etc) until their expiration
dates.
I have PizzaV1.0.0 API, which strategy does it use to generate a new V2.0.0 version and keep both in ESB.
If version the CAR, the duplicity of APIs and Sequences.
I have not found a way to version the APIs in eclipse, I need to version the API and some sequences that have changed.
In API Manager I created a new version, now I have two versions published.
What versioning strategy do you use in ESB to stay in sync with API Manager?
Maybe this post can help you
http://nandikajayawardana.blogspot.com.br/2014/02/proxy-service-version-management-with.html
I do what they describe and it is working great.