# \[Ignition 8.0.7\] Windows Launchers cannot be configured to use Windows Certificate Store **URL:** \ **Category:** Ignition\ **Tags:** ignition80\ **Created:** [January 29, 2020, 5:58pm UTC](https://forum.inductiveautomation.com/t/ignition-8-0-7-windows-launchers-cannot-be-configured-to-use-windows-certificate-store/31724 "2020-01-29T17:58:20Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [January 29, 2020, 6:03pm UTC](https://forum.inductiveautomation.com/t/ignition-8-0-7-windows-launchers-cannot-be-configured-to-use-windows-certificate-store/31724/2 "2020-01-29T18:03:51Z")
Can your IT automation place the certificates that need to be trusted into the `$USER/.ignition/clientlauncher-data/certificates` folder on machines that will be launching clients and designers? The same can be done on the gateway using `$IGNITION/data/certificates/supplemental` as well. Then you don't have to mess with using the windows certificate store. > [@Designer Launcher SSL](http://forum.inductiveautomation.com/t/designer-launcher-ssl/24199/2): > > @Tbthomps The new launchers have their own embedded JVM which complicates things. Is your certificate self-signed or signed by a CA? If you have a self-signed (or a cert signed by a CA that isn’t included in Java’s default keystore) you can add the certificate for the gateway to the .ignition/clientlauncher-data/certificates directory. Any x.509 certificate should work. The next time you open the launcher, the certificate will be added to the default java keystore (including any JVM’s that are … --- _[View the full topic](https://forum.inductiveautomation.com/t/ignition-8-0-7-windows-launchers-cannot-be-configured-to-use-windows-certificate-store/31724)._