PKIX path building failed: unable to find valid certification path to requested target when accessing Plugin Repository
0 reputation · 21 Dec 2021, 10:49 UTC
The goal is to allow CLion to trust a self‑signed or corporate‑issued certificate for HTTPS access to the Plugin Repository without modifying the global JDK cacerts truststore, which would affect all Java‑based tools bundled with the IDE.
As of CLion 2024.3 the IDE does not provide a UI for managing custom trust stores; the only documented approach is to set the -Djavax.net.ssl.trustStore and -Djavax.net.ssl.trustStorePassword VM options, which apply to the entire JVM and may cause unintended security warnings for other components.
What mechanisms exist to scope a custom trust store to the CLion instance or specifically to plugin‑repository connections? Can CLion be launched with a per‑IDE truststore that does not alter the bundled JDK? Are there any planned UI enhancements to manage custom CAs for plugin repository access?
clion