Support for self-signed certs?

[Panoplos]

When developing locally, it is important to support self-signed certs. I believe adding this is quite simple and can be disabled by default for security reason.

[martijnwalraven]

Do you mean supporting self-signed certs for downloading the schema?

[Panoplos]

Yes

[Panoplos]

Note that I implemented this in gql2flow (before knowing about this tool).
joarwilk/gql2flow#30

[martijnwalraven]

@Panoplos: Seeing as you've already implemented this, a PR would be very welcome!

[xrd]

I think this is done, via the -K true switch.

insecure: {
        alias: 'K',
        describe: 'Allows "insecure" SSL connection to the server',
        type: 'boolean'
      },

[schleumer]

@xrd even when using --insecure, --insecure=true, -K, -K true, or any other variation i still get error: Error while fetching introspection query result: Protocol "http:" not supported. Expected "https:", i think that flag means that it can be a insecure connection somehow but not a self-signed cert or HTTP, a look at source: https://github.com/apollographql/apollo-codegen/blob/master/src/downloadSchema.ts#L20 and removing that line and its reference helped me to download a schema via HTTP

Edited:

After rereading the code noticed that --insecure actually forces connections through HTTPS 😅

[maarekj]

Has --insecure option disappeared ?

[SimonCropp]

i have the same question as @maarekj

[robertomg]

We need to support this feature. Our team is also using a self-signed certificate for development.