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

[lsp-server] 🐞 rejectUnauthorized doesn't work as advertized #3596

Open
1 task done
TimMensch opened this issue May 9, 2024 · 0 comments
Open
1 task done

[lsp-server] 🐞 rejectUnauthorized doesn't work as advertized #3596

TimMensch opened this issue May 9, 2024 · 0 comments
Labels
bug lsp-server graphql-language-service-server

Comments

@TimMensch
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

If you have a self-signed certificate on your GraphQL server, the "rejectUnauthorized" flag is supposed to allow the VS Code GraphQL Language Feature Support extension to accept a self-signed certificate.

Ideally, the option would allow us to select a root certificate to trust, but at the very least the documented option should allow self-signed certificates to work.

At present, every single interaction results in:

[Error - 8:48:26 PM] Request textDocument/hover failed.
  Message: Request textDocument/hover failed with message: unable to verify the first certificate
  Code: -32603 

Expected Behavior

It should work with a self-signed cert. 'nuff said.

Steps To Reproduce

Same setup as this older bug:

#451

In other words:

  1. Create a self-signed certificate.
  2. Serve GraphQL from that server.
  3. Note that the GraphQL language server refuses to connect.

The VS Code extension has an option "vscode-graphql.rejectUnauthorized" that is supposed to set the language server to accept self-signed certificates. It doesn't work.

Environment

  • LSP Server Version: Heck if I know. The output window has nothing in it resembling a version number. Whatever comes with the latest version of the VS Code extension.
  • OS: Windows 11
  • LSP Client: vscode (graphql.vscode-graphql-0.9.3)

Anything else?

I also tried the prerelease version. No difference in behavior.

@TimMensch TimMensch added bug lsp-server graphql-language-service-server labels May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug lsp-server graphql-language-service-server
Projects
None yet
Development

No branches or pull requests

1 participant