-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Closed
Labels
waiting for infoWaiting for feedback from the userWaiting for feedback from the user
Description
Probably a user error, but maybe the documentation/output could be improved.
I used mkcert
successfully on my local machine, then tried the same on our CI server (Debian stretch) and got:
root@ci:~# export JAVA_HOME="$(dirname $(dirname $(readlink -f $(which java))))"
root@ci:~# echo $JAVA_HOME
/usr/lib/jvm/java-11-openjdk-amd64
root@ci:~# mkcert -install
Using the local CA at "/root/.local/share/mkcert" ✨
The local CA is now installed in the system trust store! ⚡️
No mention of the java trust store. It would be good if there was some output/warning about what went wrong. It took me a while to figure out that apparently I shouldn't run mkcert
as root. Running the same commands as a different user works (and asks for sudo
password).
Btw. when running mkdir -install
a second time, there is also no mention of the java trust store.
First time:
user@ci:~$ mkcert -install
Using the local CA at "/home/user/.local/share/mkcert" ✨
Installing to the system store is not yet supported on this Linux 😣 but Firefox and/or Chrome/Chromium will still work.
You can also manually install the root certificate at "/home/user/.local/share/mkcert/rootCA.pem".
The local CA is now installed in Java's trust store! ☕️
Second time:
user@ci:~$ mkcert -install
Using the local CA at "/home/user/.local/share/mkcert" ✨
Installing to the system store is not yet supported on this Linux 😣 but Firefox and/or Chrome/Chromium will still work.
You can also manually install the root certificate at "/home/user/.local/share/mkcert/rootCA.pem".
Metadata
Metadata
Assignees
Labels
waiting for infoWaiting for feedback from the userWaiting for feedback from the user