starred/Proxyman

Fork 0

mirror of https://github.com/ProxymanApp/Proxyman.git synced 2026-04-26 16:45:57 +03:00

[GH-ISSUE #737] install-certificates-java.sh Doesn't work with JVMs installed via SDKMAN #732

New issue

Open

opened 2026-03-03 19:21:23 +03:00 by kerem · 12 comments

kerem commented

2026-03-03 19:21:23 +03:00

Owner

Originally created by @jeremyross on GitHub (Dec 22, 2020).
Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/737

Originally assigned to: @NghiaTranUIT on GitHub.

Proxyman version? 2.15.0 (21500)

macOS Version? 10.15.7 (

Steps to reproduce

Run install-certificates-java.sh

Expected behavior

Installs cert into JVM

/usr/libexec/java_home only returns JVMs installed by Mac OS. SDKMAN is a popular alternative way of installing and managing JVMs. I was able to modify install-certificates-java.sh and get this working:

home=/Users/jeremyross/.sdkman/candidates/java/current

A better solution would be to take into account /usr/libexec/java_home, SDKMAN, and probably homebrew installs as well.

Originally created by @jeremyross on GitHub (Dec 22, 2020). Original GitHub issue: https://github.com/ProxymanApp/Proxyman/issues/737 Originally assigned to: @NghiaTranUIT on GitHub. ### Proxyman version? 2.15.0 (21500) ### macOS Version? 10.15.7 ( ### Steps to reproduce 1) Run install-certificates-java.sh ### Expected behavior Installs cert into JVM `/usr/libexec/java_home` only returns JVMs installed by Mac OS. SDKMAN is a popular alternative way of installing and managing JVMs. I was able to modify install-certificates-java.sh and get this working: ``` home=/Users/jeremyross/.sdkman/candidates/java/current ``` A better solution would be to take into account `/usr/libexec/java_home`, SDKMAN, and probably homebrew installs as well.

kerem added the

bug

✅ Done

labels

2026-03-03 19:21:23 +03:00

kerem commented

2026-03-03 19:21:24 +03:00

Author

Owner

@NghiaTranUIT commented on GitHub (Dec 22, 2020):

Thanks for the solution. I will checkout the SDKMAN and support it 🙌

@NghiaTranUIT commented on GitHub (Dec 22, 2020): Thanks for the solution. I will checkout the SDKMAN and support it 🙌

kerem commented

2026-03-03 19:21:24 +03:00

Author

Owner

@NghiaTranUIT commented on GitHub (Dec 24, 2020):

It's fixed with this beta build: https://proxyman.s3.us-east-2.amazonaws.com/beta/Proxyman_2.15.1_Support_SDKMAN_JAVA.dmg

Thank you for opening the ticket 🎉

@NghiaTranUIT commented on GitHub (Dec 24, 2020): It's fixed with this beta build: https://proxyman.s3.us-east-2.amazonaws.com/beta/Proxyman_2.15.1_Support_SDKMAN_JAVA.dmg Thank you for opening the ticket 🎉

kerem commented

2026-03-03 19:21:24 +03:00

Author

Owner

@jeremyross commented on GitHub (Aug 18, 2021):

This is not working. The script fails on this line:

HOME=$(/usr/libexec/java_home)

with this message:

Unable to find any JVMs matching version "(null)".
No Java runtime present, try --request to install.

So, the script never gets to the part where it checks JAVA_HOME and SDKMAN.

@jeremyross commented on GitHub (Aug 18, 2021): This is not working. The script fails on this line: ``` HOME=$(/usr/libexec/java_home) ``` with this message: > Unable to find any JVMs matching version "(null)". > No Java runtime present, try --request to install. So, the script never gets to the part where it checks JAVA_HOME and SDKMAN.

kerem commented

2026-03-03 19:21:24 +03:00

Author

Owner

@NghiaTranUIT commented on GitHub (Aug 19, 2021):

Thanks for getting back @jeremyross. I will revisit the script to see how to fix it 👍

If you don't mind, you can manually fix the script at

/Applications/Proxyman.app/Contents/Frameworks/ProxymanCore.framework/Versions/A/Resources/install-certificates-java.sh

By removing the part:

# Default directory
HOME=/usr/libexec/java_home
if [ -f "$HOME" ]; then
    HOME=$(/usr/libexec/java_home)
    if [[ -z "$HOME" ]]; then
        echo "Could not find /usr/libexec/java_home!"
    elif [[ -n "$HOME" ]]; then
        echo "=> Found $HOME"
        install_certificate $HOME
    fi
fi

It will work with the SDKMAN

@NghiaTranUIT commented on GitHub (Aug 19, 2021): Thanks for getting back @jeremyross. I will revisit the script to see how to fix it 👍 If you don't mind, you can manually fix the script at ``` /Applications/Proxyman.app/Contents/Frameworks/ProxymanCore.framework/Versions/A/Resources/install-certificates-java.sh ``` By removing the part: ``` # Default directory HOME=/usr/libexec/java_home if [ -f "$HOME" ]; then HOME=$(/usr/libexec/java_home) if [[ -z "$HOME" ]]; then echo "Could not find /usr/libexec/java_home!" elif [[ -n "$HOME" ]]; then echo "=> Found $HOME" install_certificate $HOME fi fi ``` It will work with the SDKMAN

kerem commented

2026-03-03 19:21:24 +03:00

Author

Owner

@jamesdh commented on GitHub (Aug 28, 2022):

Pinging this issue to remind someone that it's still an issue. SDKMAN is a very popular tool among Java developers for installing modern JDK's.

@jamesdh commented on GitHub (Aug 28, 2022): Pinging this issue to remind someone that it's still an issue. SDKMAN is a very popular tool among Java developers for installing modern JDK's.

kerem commented

2026-03-03 19:21:24 +03:00

Author

Owner

@NghiaTranUIT commented on GitHub (Aug 29, 2022):

Thanks @jamesdh for reminder. I will look on it and send a beta soon 👍

Just wondering:

Which SDKMan version you're using?
And the path? echo $SDKMAN_DIR

@NghiaTranUIT commented on GitHub (Aug 29, 2022): Thanks @jamesdh for reminder. I will look on it and send a beta soon 👍 Just wondering: - Which SDKMan version you're using? - And the path? `echo $SDKMAN_DIR`

kerem commented

2026-03-03 19:21:24 +03:00

Author

Owner

@jamesdh commented on GitHub (Aug 29, 2022):

@NghiaTranUIT SDKMAN 5.16.0. It's worth mentioning that SDKMAN automatically keeps itself up to date, so most people that use it will be on either the newest version or maybe one version back.

Via the SDKMAN setup script, SDKMAN_DIR="$HOME/.sdkman", hence in my case on macOS it's /Users/jamesdh/.sdkman

@jamesdh commented on GitHub (Aug 29, 2022): @NghiaTranUIT SDKMAN 5.16.0. It's worth mentioning that SDKMAN automatically keeps itself up to date, so most people that use it will be on either the newest version or maybe one version back. Via the [SDKMAN setup script](https://get.sdkman.io), `SDKMAN_DIR="$HOME/.sdkman"`, hence in my case on macOS it's `/Users/jamesdh/.sdkman`

kerem commented

2026-03-03 19:21:24 +03:00

Author

Owner

@NghiaTranUIT commented on GitHub (Aug 30, 2022):

Hey @jamesdh let's try this beta build: https://proxyman.s3.us-east-2.amazonaws.com/beta/Proxyman_3.8.0_Fix_sdkman.dmg

It works fine with sdkman 👍

@NghiaTranUIT commented on GitHub (Aug 30, 2022): Hey @jamesdh let's try this beta build: https://proxyman.s3.us-east-2.amazonaws.com/beta/Proxyman_3.8.0_Fix_sdkman.dmg It works fine with sdkman 👍 <img width="682" alt="Screen Shot 2022-08-30 at 15 52 50" src="https://user-images.githubusercontent.com/5878421/187394093-a304a7f0-1905-4089-9c70-0e0591875e16.png">

kerem commented

2026-03-03 19:21:24 +03:00

Author

Owner

@jamesdh commented on GitHub (Sep 1, 2022):

@NghiaTranUIT if I do brew uninstall proxyman will that sufficiently remove any previously installed certificates so that I can retry the install w/ your beta build?

@jamesdh commented on GitHub (Sep 1, 2022): @NghiaTranUIT if I do `brew uninstall proxyman` will that sufficiently remove any previously installed certificates so that I can retry the install w/ your beta build?

kerem commented

2026-03-03 19:21:24 +03:00

Author

Owner

@NghiaTranUIT commented on GitHub (Sep 1, 2022):

Yes, it's sufficient. It will delete all Proxyman data, certificate in the disk + Keychain (Ref: github.com/Homebrew/homebrew-cask@212b287c3e/Casks/proxyman.rb (L20))

You can simply do it by the GUI: Visit Help Menu -> Advanced -> Factory Reset.

Note: It's brew uninstall proxyman, not proximal ✅

@NghiaTranUIT commented on GitHub (Sep 1, 2022): Yes, it's sufficient. It will delete all Proxyman data, certificate in the disk + Keychain (Ref: https://github.com/Homebrew/homebrew-cask/blob/212b287c3e8775f2bf320d2be09087ba7e713e6f/Casks/proxyman.rb#L20) You can simply do it by the GUI: Visit Help Menu -> Advanced -> Factory Reset. ---------- Note: It's `brew uninstall proxyman`, not `proximal` ✅

kerem commented

2026-03-03 19:21:24 +03:00

Author

Owner

@jamesdh commented on GitHub (Sep 1, 2022):

@NghiaTranUIT can confirm it appears fixed!

@jamesdh commented on GitHub (Sep 1, 2022): @NghiaTranUIT can confirm it appears fixed!

kerem commented

2026-03-03 19:21:24 +03:00

Author

Owner

@karljamoralin commented on GitHub (Dec 10, 2024):

~~Hi @NghiaTranUIT ! Is the fix for this already in one of the stable releases?~~ Yes, it works with version 5.11.0

@karljamoralin commented on GitHub (Dec 10, 2024): ~~Hi @NghiaTranUIT ! Is the fix for this already in one of the stable releases?~~ Yes, it works with version `5.11.0`