Schema Reference Errors When Creating API Products from APIs That Use allOf

[AselaPathirage]

Current Limitation

It has been observed that when creating API products from APIs, "token does not exist" errors are encountered even though the schemas are defined in the API definition. Upon investigation, it was found that schemas referenced within object properties under an allOf construct are not being included in the API definition of the created API product.

Steps to reproduce:

• Deploy an API using the testAPI.json file. testAPI.json
• Create and deploy an API product using the POST resource of that API.

Suggested Improvement

This should ideally be supported in APIM when creating API Products as the OpenAPI specification explicitly supports the use of 'allOf'.

Version

4.1.0