Hi everybody,We're using Portal 4.2 and we want to go live, but we have a problem and maybe someone else has already solved it.
We don’t want anyone could create Apis on the Portal and sync these Apis to the Production Gateway (that could be a security issue for us).
I know that we could use scripted deployment type on the enrol but so all the Apis created on the Gateway will never sync to the Portal; scripts works only for the api created on the Portal and all ours Apis are created on the Gateway (not on the Portal).
You are looking for Gateway Published API's:
Publish APIs - CA API Developer Portal - 4.2 - CA Technologies Documentation
thanks for the reply; I know how to publish Apis from Gateway to Portal .. the problem is the deployment type I select on enrolling the Gateway with the Portal: Automatic will sync every Apis (and we don't want that), Scripted will sync (using a script) only Portal Apis to the Gateway but not the Gateway Apis to the Portal.
We don't want anyone can create (and sync) Apis from Portal to Gateway; our scenario is only to have Gateway Managed Apis... but how do we sync them (using scripted deployment model) ?
Not exactly understand your use case here. You don't want API owners to publish there own API's, only publish API's from the Gateway?
Docops describes for enrolling a Gateway:
Yes .. the only APIs on the Portal must be APIs from the Gateway, but if we use Automatic deployment type, if someone (with admin user) create an API to the Portal, this API will be synced to Gateway and we don't want this behaviour.
To use Gateway Published API, you must use Automatic Deployment.
If you look at On-Demand Deployments e Scripted Deployments documentation, it states it is useful only for Portal Publish API.
Deploy Proxy with On-Demand Deployments - CA API Developer Portal - 4.2 - CA Technologies Documentation
Deploy Proxy with Scripted Deployments - CA API Developer Portal - 4.2 - CA Technologies Documentation
While a Gateway administrator can publish an API and it will be synchonized with API Portal, it will not be read in API Portal.
A Portal Admin or API Owner will need to setup the api in the portal.