I have REST API app running on https://fqdn:8443/aa-restapi/doc/ . But Base URL shows up as ip:8443/aa-restapi/ca/advancedauth/v1. Shemes only show HTTP. When clicking Try it out, a REST API request is sent to i.e. http://ip:http://ip:8443/aa-restapi/ca/advancedauth/v1/admin/authtokenThe same for a generated curl commandcurl -X POST "http://ip:8443/aa-restapi/ca/advancedauth/v1/admin/authtoken" -H "accept: application/json" -H "content-type: application/json" -d ...
Is there a way to fix it, a conf file?
After looking internally I found that there is a defect opened on this issue and the latest on the defect notes is below:
You will be updated via case with the final conclusion.
I have had a ticket opened for a month and haven't received any update that there is a pending defect for this already. In the current state without ssl, Swagger is a dangerous tool because the credentials are not protected in the transit. The documentation is pretty frustrating as well, because it says as below until you find a "foot print" with Limitations.
The base URL for the REST API is defined by the protocol, host, and application context on the root level of the API specification.
The base URL used for all operations is formatted as follows:
The components of the base URL are:
I tested a dev fix and Swagger is fine now.