Is there a way to use the OAS Validation Policy if the API Proxy and OAS base path is different?

[apiguru1]

I want to use the OAS Validation Policy. Unfortunately, the policy fails since the API Proxy and OAS base paths are different. Is there a way to use the OAS Validation Policy if the API Proxy and OAS base path is different? Any suggestions?

[dchiesa1]

Hmmm

The documentation for the policy states that the policy "Validates the basepath defined by the API proxy; ignores the basepath specified in the OpenAPI Specification."

So what you are describing... shouldn't happen? 

Do you have a small proxy that reproduces this?  Something that includes a small (super simple) OAS and a proxy with a different basepath and maybe one conditional flow? If so , can you attach it here?

[apiguru1]

Thank you very much for your quick reply.

The problem is that the request path (minus the basepath) matches none of the path patterns defined in the OpenAPI Specification.

The basepath specified in the Open API specification is:
https://sandbox.api.ato.gov.au/super/v1

The basepath specified in the API Proxy specification is:
https://sandbox.api.ato.gov.au/super/v1/clients/ABN/{abn_payer}/payees/TFN/{tfn_payee}/stapledSuperF...

The request path is:
https://sandbox.api.ato.gov.au/super/v1/clients/ABN/{abn_payer}/payees/TFN/{tfn_payee}/stapledSuperF...

Open API specification:
https://apiportal.ato.gov.au/apis/106/specification

Because of internal routing rules, it is not possible to change the basepath specified in the API Proxy. What is the best way to face this problem? For e.g. is there a way to suppress the error message?

[alexnoctis76]

You ever find a solution?