Interactive JVM Selection for "Install Certificate on Java VMs"

Open
#2,554 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start from Certificate → Install Certificate on Java VMs → Run Script and run /usr/libexec/java_home -V to inspect the JVM output. Define how detected installations are parsed and presented for single, multiple, or all-JVM selection. Done means the certificate is installed into every selected JVM path and the existing workflow remains usable.

Written by the indexing model from the issue text.

Description

enhancement

Description

When installing a certificate via
Certificate → Install Certificate on Java VMs → Run Script,
Proxyman automatically uses the current JAVA_HOME.
It would be more flexible if Proxyman allowed users to select which Java VM(s) to install the certificate into.

Proposed Enhancement

  1. Proxyman should execute:
    /usr/libexec/java_home -V
  2. Parse and display all detected JVM installations.
  3. Allow the user to:
  • Select a specific JVM
  • Select multiple JVMs
  • Or choose “Install to all JVMs”

After selection, Proxyman should install the certificate into each chosen JVM path.

Why this is important

Many developers have multiple JDKs installed (e.g., Java 8, 11, 17, 21).
Automatically picking only the current JAVA_HOME can lead to inconsistent behavior across tools and build systems.
Allowing interactive selection would make certificate installation more reliable and user‑controlled.

Dominant language
No language data
Stars
7k
Forks
237
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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.

More from ProxymanApp/Proxyman

All issues in ProxymanApp/Proxyman

Similar issues

More Desktop Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.