API policy to restrict the API usage (endpoints and operations ) as per the swagger specifications (OpenAPI 3.0 spec)?
Portal 5.2 and Gateway 11.x
Current version of portal doesn’t have a feature to important/read OpenAPI spec. The feature is under consideration, but not something in 5.3
Workaround/possibility
Potentially from Policy Manager use the wizard “Publish OpenAPI Service Wizard” to create an example and then copy/paste the policy to reuse parts of it.
The policy template itself ultimately has to be an encapsulated assertion (i.e. a policy fragment turned into an encapsulated assertion) so it cannot be a service policy.
Review docs link:
Then follow the step in Portal docs to “Add Policy Templates using Policy Manager”
This can now be used in Portal published API
NOTE For this template to be used on other Gateway Proxies the encapsulated assertions must be migrated to the other Gateway’s (i.e. GMU)