Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add ability to trust a self-signed certificate #156

Closed
m4rcelpl opened this issue Dec 29, 2022 · 5 comments
Closed

Add ability to trust a self-signed certificate #156

m4rcelpl opened this issue Dec 29, 2022 · 5 comments
Labels
enhancement New feature or request

Comments

@m4rcelpl
Copy link

Hi,
Now if I want to use internal API with self-signed certificate, i can't.
My suggestion is a checkbox like in postman.
Zrzut ekranu 2022-12-29 o 09 07 20

@neon-balcony neon-balcony added the enhancement New feature or request label Dec 29, 2022
@Simonaaaa-C
Copy link

Simonaaaa-C commented Jan 18, 2023

Hi, this feature is supported now. Please check and update to the latest version v1.1.4. Thanks for your advice and patience.
image

@virtzilla
Copy link

I only see this option available if I look at the REST API option under the global Data Sources. I really want to see the option under an individual query in my app when selecting the "REST Query" option within it. Is there a means to make it appear there, or do I have to use a global?

I was thinking I had an old version and after verifying I had the latest, thought something was amiss with my deployment after seeing your screen shot and not seeing it in there.

@neon-balcony
Copy link
Contributor

Hey @virtzilla, first we use the idea of data source to store credentials and common settings for a bunch of queries. For example you can create a REST API data source with common URL prefix (e.g. https://my_api.com/api/) and shared headers (e.g. X-REQUEST-TOKEN token-cpsitnvj34) so that all queries that originated from it don't need to declare those on their own.

Second, as per the REST API Query you mentioned to create REST queries, you can think it as a system predefined REST API data source with empty settings inside, and it can relieve users from creating empty dummy REST API data sources.

At last for the SSL Cert Verfication setting, we would consider it as a data source level feature and you can only configure that in a newly created data source rather than the predefined one. The good news is that all subsequent queries which need this configuration can benefit from this data source.

@virtzilla
Copy link

In my use case, I have dynamic endpoints that I want to define on the fly for the API endpoints (appliances) - thus trying to avoid "predefined" data sources. I have a form value for the hostname, thus the path I was taking.

At last for the SSL Cert Verfication setting, we would consider it as a data source level feature and you can only configure that in a newly created data source rather than the predefined one

Stepping back, I think such a setting equally applies in both areas and shouldn't be limited to the data source level. I know at least for me on my quest, I wasted a fair amount of time trying to find the newly referenced option where it wasn't (and that led me down a path of why I wasn't seeing it) where I would expect to.

@neon-balcony
Copy link
Contributor

Got it, in this case I think you can still create an REST API data source with empty host/path and SSL Cert Verfication configured.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants