[Feat] Support secure storage for secrets (API tokens) in MCP server configuration

Ouverte
#518 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
15/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
java
Domaine
security

Piste de recherche

The payload names no files, so start by locating where the MCP server configuration is read and saved in the plugin. The issue asks for two things: MCP configs that reference secrets instead of holding them, and storage through Eclipse Secure Storage, modelled on VS Code's inputs mechanism. Work out the design before coding. Done means a token can be referenced rather than typed in plain text. This is design work, so discuss the approach with maintainers first.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

enhancement

Is your feature request related to a problem? Please describe.
I'm frustrated that MCP server credentials, such as API tokens for Jira, have to be entered directly into the MCP configuration in Copilot for Eclipse. There is currently no other way to provide them: the configuration doesn't support referencing environment variables, and MCP servers don't pick up OS environment variables either. The token must be saved in plain text in the configuration.

As a result, these tokens are:

  • readable by any process or user with access to the Eclipse configuration files
  • at risk of being exposed through backups, synced settings, screenshots, or screen sharing

As MCP servers become more common, users are handing more and more tokens to AI agents, so this is a growing security concern. In corporate environments, storing credentials in plain-text files may also violate security policies, which can prevent teams from using MCP servers in Eclipse at all.

Describe the solution you'd like
Allow MCP configurations to reference secrets instead of containing them, and store the actual values in a secure way. One approach could be to save it using Eclipse's built-in Secure Storage.

The integration into the MCP mechanism could be similar to VS Code's inputs mechanism (from the local harness).

Describe alternatives you've considered
Not even the Copilot harness in VS Code supports the "inputs" mechanism yet (as opposed to the local harness). To at least reach parity with the Copilot harness in VS Code, support for environment variables could be added.

Additional context
None so far

Langage dominant
Java
Étoiles
128
Forks
70
Merge moyen
5 j 20 h
PR mergées (30 j)
3

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de microsoft/copilot-for-eclipse

Toutes les issues de microsoft/copilot-for-eclipse

Issues similaires

Plus d'issues Java

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.