APIs created via super tenant publisher are not available in developer portal/ publisher of other tenants
I am using wso2 API manager 3.1.0 and wso2 IS as KM 5.10.0 . I created the tenants in API manager's carbon console. When I created some APIs via super tenant's publisher portal and set the subscription availability to specific tenants as shown in below figure. Also the developer portal visibility is set to public.
But when I login to the developer portals of one of the tenant to which I configured the subscription to be availble in previous step I am unable to see the API. Is this a Bug?
If you checked for the API in the specific tenant's Developer Portal, the API will not be visible. Since the API is created by the super tenant which is carbon.super, the API is only accessible from the carbon.super developer portal space. If you login as a different tenant to the carbon.super developer portal space, then you will be able to see the API.
The API will be visible and subscribable for the tenants that you have specified under "Subscription Availability" section in Publisher given their visibility is Public according to your scenario. For this you have to login to carbon.super Developer Portal Space.
See the image below where you can select the tenant developer portal you need to log into. Try logging into carbon.super space with the specific tenant credentials.
- Error showing Transport Level Information error in SOAP Message
- Migrating from WSO2 Enterprise Integrator to Micro Integrator
- Using script mediator in WSO2 Micro Integrator 4.3
- Deploying CApp to Service Catalog fails on malformed JSON error
- Error while launching run and debug: Build process failed - wso2 micro integrator with Visual Studio
- WSO2 Error while building Passthrough stream java.lang.StringIndexOutOfBoundsException
- Extracting binary as base64 String results in incomplete file?
- WSO2 Microintegrator: Error - Mediator from connector File not recognized
- WSO2 - Failure when building the Data Mapper
- WSO2 Micro Integrator: How to handle "application/json; odata.metadata=minimal" content-type from backend?
- WSO2 has not a bin directory
- WSO2 Large File Handling
- Is Endpoint Security Authentication in WSO2 APIM Done per API or per request?
- Can I use the dashboard the WSO2 DAS from other application java
- Adding HTTP security headers to WSO2 APIM (4.1.0) via deployment.toml config
- Compatibility Issue: WSO2 MI 4.1 with MongoDB Connector v2.0.0 and MongoDB 6.x Driver
- How to Access Fields in application/vnd.oracle.adf.resourceitem+json Response in WSO2 Integration Studio?
- WSO2 Multiple Gateway deployment production/sandbox endpoints
- Is there a way to run three instances of WSO2 AM in one localhost?
- CORS Configuration not working in WSO2 API Manager for Oauth2/token API
- WSO2 - Identity server 6.1.0 - Force user to change his password on first login
- OSGI Bundling issue while upgrading WSO2 APIM 3.2 to 4.3
- WSO2 API Manager 4.2 with AWS ALB : Problems with mTLS Authentication Setup
- WSO2 API Manager (wso2am-4.3.0) - Error When Invoking APIs After Disabling OpenAPI Validations
- WSO2 Kafka Consume messages from topic issue
- WSO2 API Manager (wso2am-4.3.0) - How to Disable OpenAPI Validation When Importing Swaggers?
- "keytool error: java.io.IOException: Invalid keystore format"
- wso2 api manager elk based analytics
- How to enable TLS 1.1 in wso2 APIM 4.2
- WSO2 API Manager (wso2am-2.1.0) - How to implement passwordless authentication using WSO2 APIM and Microsoft Authenticator App?