multi-tenancy for portal applications

book

Article ID: 140842

calendar_today

Updated On:

Products

API MANAGEMENT SAAS CA API Management SaaS

Issue/Introduction

We use in our portal implementation different proxies (api gateways on different datacenters).

So when we deploy an api we use the on demand method, to select on which proxies the api should be deploy only.

However we notice when creating a new application for an api deployed only on one proxy , the application (client_id/client_secret) (with portal sync application) is created on all gateways (on the otk database).

Can we make sure an application is only created on the gateway were the api is deployed.

From organisational and security perspective, application should not be synced to all gateways..

 

 

 

Environment

Release : 4.3.2

Component : API MANAGEMENT SaaS

Resolution

This feature is being considered for Portal 4.5