OpenAPI editor utilizes local network client resources
Problem to solve
Try it out! Feature in Swagger rendered files do not connect to endpoints accessible only on my local network.
With the addition of #19515 (closed), swaggers are rendered within the UI providing a huge amount of value to developers who are using swagger as part of their API creation process. As with most enterprises however, most backends are only accesible on a local corporate network, this means that anyone using gitlab.com for their enterprise are not able to use the live "Try it out!" feature right from the browser to experiment with calls/parameters.
Proxy requests sent by the rendered swagger to use the local network from the client using the browser rather than the server.
Permissions and Security
Assuming there would have to be some sort of security acceptance requirement to give the website I'm visiting (swagger through gitlab.com) access to be able to contact my local network's resources.
- It will need cross-browser testing.
- There will be security implications.
What does success look like, and how can we measure that?
Swagger renders gitlab.com file UI browsing can hit local network endpoints accessible from my client.
What is the type of buyer?