# Designer Launcher SSL

**URL:** <https://forum.inductiveautomation.com/t/designer-launcher-ssl/24199>\
**Category:** Ignition Early Access\
**Created:** [April 17, 2019, 2:10pm UTC](https://forum.inductiveautomation.com/t/designer-launcher-ssl/24199 "2019-04-17T14:10:45Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![jcoffman](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jcoffman/32/6429_2.png) [@jcoffman](https://forum.inductiveautomation.com/u/jcoffman)\
**Post date:** [April 17, 2019, 3:08pm UTC](https://forum.inductiveautomation.com/t/designer-launcher-ssl/24199/2 "2019-04-17T15:08:23Z")

</div>

@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 retrieved from gateways to launch clients etc)

Thanks,  
Jonathan C

---

_[View the full topic](https://forum.inductiveautomation.com/t/designer-launcher-ssl/24199)._