Layer7 API Management

Hi,

I published APIs with the sample voonair.wadl which I got from the early Gateway training. The publishing is successful. But when I tried to explore one of the API with API Explorer, I got error "API Explorer requires secure HTTPS connections. Please ensure your API descriptor file uses only HTTPS."

Then I modified the <resources base="http://voonair.l7tech.com:6060/voonair"> in the wadl file to <resources base="https://voonair.l7tech.com:6060/voonair"> whereI changed http to https and republished as a new API. The Location of API still show http://voonair.l7tech.com:6060/voonair on the publish page after I upload the wadl file. I changed it to https and saved, but still got the same error when trying in API Explore again.

Anyone can help?

Thanks

Hi,

Adding ‘s’ to http won’t make service https, you have to make change at port level.

In policy manager listen port section, you have to change the protocol from http to https.

Regards,

Mahesh

Hi Mahesh,

Thanks for the quick response. If I understand correctly, the API Explore will send request to the proxy Gateway where the API is deployed to, and proxy Gateway will route the request to the backend service whose URL is defined in the Location of API.  

The https 8443 and 9443 are listening by default in the Gateway. And I can call the same API from browser to Gateway with https successfully.

Yang

Yes right.

Regards,

Mahesh

Hi Mahesh,

Maybe I didn't wrote clearly in previous reply. I can call the same API from browser to Gateway with https successfully but I still got the same error while using API Explore.

Yang

Hi Yang,

In the wadl file you are using 6060 port please change it to 8443 port in the wadl file and try again.

<resources base="http://voonair.l7tech.com:6060/voonair">  change the resource base to 

<resources base="https://voonair.l7tech.com:8443/voonair"> 

and try.

Please correct me if i am wrong.

Regards,

Irfan

Hi Irfan,

I tried but got the same error. Not sure if this error is caused by API Explorer checking the API definition in Portal or Gateway.   

Thanks

Yang

Hi,

Follow below steps and Check

*     Load the blackened api wsdl/swagger/wadl to Soap UI , Change the Endpoint to Gateway i.e. which you will enter in proxy field  while API creation(Note- API path should be unique)

*     Export the swagger/wadl from Soap Ui

*     Create new API on portal(In proxy url enter gateway url i.e. one entered while creating swagger/wadl and in Location- Enter blackened URL

*     On Gateway- Check weather API is synchronised or not, once done check using Soap UI weather you are able to get proper response from newly created API or not

*     Now Go to API explorer and Check 

Regards,

Mahesh

Could you please clarify what you mean by "Blackened api"? I have the same problem as OP using a .json file containing the swagger docs.