Layer7 API Management

 View Only
  • 1.  validate openapi document assertion failure?

    Posted Nov 24, 2021 04:30 AM
    Edited by Michael Mueller Nov 24, 2021 04:33 AM
    Hi Team.
    I am trying to use the "validate openapi document" assertion.

    My openapi doc includes path defintions of
    ...
       path:
         /TST/my_api:

    The GW service resolutionpath is specified as /APITST/v1.0/TST/*

    The test postman call is done to https://gw:port/APITST/v1.0/TST/my_api

    The Service Base property of the assertion is specified as /APITST/v1.0*

    Unfortunately the validate assertion fails, and I don't know what I am doing wrong.
    Does anyone has any idea ?

    Thanks
    ....Michael


  • 2.  RE: validate openapi document assertion failure?

    Broadcom Employee
    Posted Nov 28, 2021 09:16 PM
    Do you get a specific error ?

    ------------------------------
    Aran White - [JobTitle]
    [CompanyName]
    [State]
    ------------------------------



  • 3.  RE: validate openapi document assertion failure?

    Posted Nov 29, 2021 02:47 AM
    Hi Aran.
    Thanks for coming back to me on this.
    The expandedPath value was set to /APITST/v1.0/TST/my_api
    which of course could not be found in the openapi spec.

    Meanwhile by more testing, I know why. The Service Base value should not include  the trailing star*.
    So , Service Base set to :  /APITST/v1.0*does not work
    But using it without the asterisk is working. Obviously the Service Base value is just removed from the beginning of the incoming service uri.
    I misunderstood the docs stating: "
    Note: The service URI must end with '/*' ..."
    Just quite clear after knowing how it works.


    Thanks and kind regards
    ....Michael