microsoft / microsoft/copilot-for-eclipse

Sign in fails

Open
#74 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Feedback source

Internal Enterprise Feedback

GitHub Copilot plugin version

GitHub Copilot 0.14.0.202601160448_nightly com.microsoft.copilot.eclipse.feature.feature.group GitHub Copilot

Eclipse IDE and version

2025-12 (4.38.0)

Platform

When trying to sign in to GitHub Copilot from the Eclipse plugin, the login process fails and it is not possible to sign in.

Steps to reproduce

Steps to reproduce:

From the GitHub Copilot plugin in Eclipse, click on Sign in.

A window opens asking to open the GitHub login page and enter a verification code.

Click to open the browser and enter the verification code on the GitHub page.

The verification in the browser completes successfully.

However, nothing happens in Eclipse after the successful verification, and the user is not signed in.

Logs (optional)

Sign in failed: org.eclipse.lsp4j.jsonrpc.ResponseErrorException: Could not log in with device flow on https://github.com/: self-signed certificate in certificate chain

Expected behavior

sign in

Actual behavior

Sign in failed: org.eclipse.lsp4j.jsonrpc.ResponseErrorException: Could not log in with device flow on https://github.com/: self-signed certificate in certificate chain

Additional information

No response

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 at the Eclipse plugin's Sign in action and device-flow request, reproducing the failure with the reported plugin and Eclipse versions. Use the reported self-signed certificate error as the initial investigation point. Done means the browser verification completes and Eclipse signs the user in successfully, with the failure covered by an appropriate regression check.

Written by the indexing model from the issue text.

Assessment

Tech stack
github, java
Domain
authentication, desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.