# Ignition Client blocked by Java Security

**URL:** <https://forum.inductiveautomation.com/t/ignition-client-blocked-by-java-security/37462>\
**Category:** Ignition\
**Created:** [August 6, 2020, 3:05pm UTC](https://forum.inductiveautomation.com/t/ignition-client-blocked-by-java-security/37462 "2020-08-06T15:05:15Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![meredithj](https://avatars.discourse-cdn.com/v4/letter/m/cc9497/32.png) [@meredithj](https://forum.inductiveautomation.com/u/meredithj)\
**Post date:** [August 6, 2020, 3:05pm UTC](https://forum.inductiveautomation.com/t/ignition-client-blocked-by-java-security/37462/1 "2020-08-06T15:05:15Z")

</div>

Hi there,

I am running an ignition 7.9.3 server and every time I launch a project, I am getting an error saying that the Ignition Client is Blocked by Java Security. The latest fix I could find for this is here:  
[https://support.inductiveautomation.com/index.php?/Knowledgebase/Article/View/102/2/ignition-client-blocked-by-java-security-settings-certificate-expired#:~:text=Ignition%20Client%20Blocked%20by%20Java%20Security%20Settings%20(Certificate%20Expired),-Posted%20by%20Dave&text=Ignition%20uses%20a%20technology%20called,launching%20clients%20from%20the%20Gateway.&text=Sometimes%20these%20error%20messages%20will,warning%20and%20launch%20a%20client](https://support.inductiveautomation.com/index.php?/Knowledgebase/Article/View/102/2/ignition-client-blocked-by-java-security-settings-certificate-expired#:~:text=Ignition%20Client%20Blocked%20by%20Java%20Security%20Settings%20(Certificate%20Expired),-Posted%20by%20Dave&text=Ignition%20uses%20a%20technology%20called,launching%20clients%20from%20the%20Gateway.&text=Sometimes%20these%20error%20messages%20will,warning%20and%20launch%20a%20client).  
but it does not mention that 7.9.3 certificates are expired now.

I can not do the java client side exception since I have too many clients and the Java Control Panel is not accessible. It also is also shown when we launch the designer.

Any Suggestions?

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [August 6, 2020, 4:24pm UTC](https://forum.inductiveautomation.com/t/ignition-client-blocked-by-java-security/37462/2 "2020-08-06T16:24:12Z")

</div>

You need to run older java or newer Ignition. v7.9.x is still under long term support, so you should consider upgrading to the latest. Side benefit of later versions is they bundle a suitable copy of java in the client launcher.

If you are still using web-launch (JNLP links), start migrating away. There’s no future for them, as support for them has been dropped in current versions of java, and dropped in Ignition v8+.

---

<div class="post-metadata">

**Author:** ![meredithj](https://avatars.discourse-cdn.com/v4/letter/m/cc9497/32.png) [@meredithj](https://forum.inductiveautomation.com/u/meredithj)\
**Post date:** [August 6, 2020, 8:16pm UTC](https://forum.inductiveautomation.com/t/ignition-client-blocked-by-java-security/37462/3 "2020-08-06T20:16:40Z")

</div>

Let me just confirm this.  
By upgrading from 7.9.3 to 7.9.14 (the current latest stable), I should have this error message disappear.  
We plan to move away from the web-launch links in the next few months after these

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [August 6, 2020, 8:40pm UTC](https://forum.inductiveautomation.com/t/ignition-client-blocked-by-java-security/37462/4 "2020-08-06T20:40:42Z")

</div>

Yes, 7.9.3 was released more than three years ago, with embedded certificates that were already a few years old at the time. Upgrading to a new version of Ignition means upgrading to new certificates, which Java shouldn’t complain about being expired.
