We are using wso2 api manager 2.1.0 and we need using tenant.
Searching in documentation we saw differences in 2.1.0 vs 2.0.0.
Are tenants supported in api manager 2.1.0?
Are all the tenant management functions available in api manager 2.1.0?
Is there any configuration that we have to do?
Would we do something else?
Thanks.
The documentation at https://docs.wso2.com/display/AM210/Multi-tenant+Architecture returns Page Not Found, it's only available at 2.0.0 Space (https://docs.wso2.com/display/AM200/Multi-tenant+Architecture)
Multitenancy is supported in both versions and all tenant features are the same in both.
You don't have to do any configuration changes.
Update: Doc is now updated with new links.
https://docs.wso2.com/display/AM210/Configuring+Multiple+Tenants
Related
How can I upgrade my project from the spark plan to the blaze plan using the firebase CLI? If it's possible.
Or maybe I can use the GCP CLI to enable billing on my project?
I don't see any relevant APIs in either the REST API for managing projects or the Admin SDK for managing projects, so I think this isn't possible today. It's a valid feature request though, so I recommend filing it.
Is there a way to disable tabs in WSO2 API Manager Store 2.2.0 API Console tabs ?
For example, i don't want SDK and Forum tabs to visible in APIM Store API Store console.
You can add a sub theme and hide these sections. Please refer https://docs.wso2.com/display/AM220/Adding+a+New+API+Store+Theme
Can we export and import multiple apis at the same time in different environments using wso2 apictl tool?
We can export multiple APIs at once using the WSO2 API Manager apictl tool. Please refer [1]. That is, you can export all APIs of a particular tenant using the command given in [1]. But importing multiple APIs is not supported.
[1] https://apim.docs.wso2.com/en/latest/learn/api-controller/migrating-apis-to-different-environments/#export-all-the-apis-of-a-tenant-at-once
Adding to what Tharika has mentioned, APICTL can only be used to migrate APIs in between different environments of the same APIM version. Migrating APIs across different APIM versions is not supported.
I've been following this guide to create developer friendly documentation for my ASP.Net REST WebApi using Swashbuckle.
However, the current version Swashbuckle.AspNetCore v2.2.0 generates a huge single page app, which is confusing for my users.
If I remember correctly, Swashbuckle was generating separate pages for each controller/method (early 2017?). My configuration looks like this:
app.UseSwaggerUI(c =>
{
c.SwaggerEndpoint("/swagger/v1/swagger.json", "API V1");
c.EnableFilter();
c.MaxDisplayedTags(5);
});
Q: Is there any way to make Swagger-UI generate separate pages for each controller and method instead of a huge single scrolling mess?
Some more Details:
VS2017
Microsoft.AspNetCore 2.0.0
Microsoft.AspNetCore.Mvc 2.0.0
Swashbuckle.AspNetCore 2.2.0
Pure WebApi - only JSON is generated, no HTML at all.
Self Hosting via Kestrel on
either Windows using net 4.6.2 (here Swashbuckle is used)
or embedded Linux using dotnet core 2.0 (Swashbuckle disabled)
Swashbuckle.AspNetCore v2.2.0 has support of arbitrary grouping of API actions into multiple Swagger documents.
Please refer the documentation here:
https://github.com/domaindrivendev/Swashbuckle.AspNetCore#generate-multiple-swagger-documents
I am trying to develop a simple customer connector for my website on microsoft flow and so far I can't see how to use a web API that is hosted on my website every article tutorial I am coming by require APIs to be hosted on Azure, also an Azure account is a prerequisite .. is it true Only azure APIs to be used for custom connectors ?
Azure is not a prerequisite for Custom Connector. I agree that most of the tutorials talk about connecting Azure hosted apps.
Microsoft flow currently supports creating custom connector with Swagger API output or postman exported data. I created a Postman collection with the API and gave the exported data as input to Microsoft flow for creating the connector.
Detailed Tutorial is available here
https://flow.microsoft.com/en-us/documentation/postman-collection/
I have the same issue, I have configured a custom connector for testing to go against this test / mock API
POST -> https://jsonplaceholder.typicode.com/posts
In the connector test it keep on hitting this URL:
https://msmanaged-na.azure-apim.net/apim/zoom.2dtest.2d002.5f43ed1d930148619c.5f4fd64f4beaca2b60/51136e9557bf4e128e0d7552ff624ebd/posts
I have never configure it to go there. No document explains how or why this would happen.