microsoft / microsoft/copilot-for-eclipse

Login/Connection Issue only with Eclipse based IDE's - No issues with VS/ VSCode

Open
#44 19 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Java
Stars
126
Forks
60
Avg merge
2d 6h
Merged PRs (30d)
5

Description

The issues mentioned by the users here are only with the eclipse based plugin and its AUTH with GitHub.

On my machine, I could get a GHCP chat working on VS Code, with all required authentication.

The same authentication gets stuck somewhere only with Eclipse or Spring Tool suite (or other Eclipse based IDE's - no issues with IntellJ or VS Code)

For example - in eclipse, I have a "Sign in to use Copilot"...

which displays a Device code and navigates to github website https://github.com/login/device,
where can i choose my GitHub account and proceed with device authentication.
supply/ paste the device code from step 1
followed by a confirmation screen ("Authorize GHCP plugin")
followed by a success & congrats page

But nothing changes on the Eclipse side.

If on Eclipse I try "Sign in to use Copilot" again, I get

Sign in failed: org.eclipse.lsp4j.jsonrpc.ResponseErrorException: Could not log in with device flow on https://github.com/: unable to get local issuer certificate

What could be the issue?

thank you

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Eclipse or Spring Tool Suite sign-in flow described in the issue, especially the device authentication at github.com/login/device and the reported local issuer certificate error. Compare the Eclipse behavior with the working VS Code flow and review the 19-comment thread for existing findings. Done means authentication completes successfully in Eclipse-based IDEs.

Written by the indexing model from the issue text.

Assessment

Tech stack
github, java
Domain
authentication, devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.