# Java 8 Security Warnings Launching Clients/Designer

**URL:** <https://forum.inductiveautomation.com/t/java-8-security-warnings-launching-clients-designer/10161>\
**Category:** Ignition\
**Created:** [June 23, 2015, 2:55pm UTC](https://forum.inductiveautomation.com/t/java-8-security-warnings-launching-clients-designer/10161 "2015-06-23T14:55:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jkiffer](https://avatars.discourse-cdn.com/v4/letter/j/ccd318/32.png) [@jkiffer](https://forum.inductiveautomation.com/u/jkiffer)\
**Post date:** [June 23, 2015, 2:55pm UTC](https://forum.inductiveautomation.com/t/java-8-security-warnings-launching-clients-designer/10161/1 "2015-06-23T14:55:03Z")

</div>

Each iteration of updates to Java JRE consistently adds at least one new security tweak. The latest Java 8 causes a prompt when launching Ignition clients and Designer. (via JNLP files)

The latest prompt:  
“The application has requested permission to establish connections to . Do you want to allow this?”

A manual tweak to the jnlp file allows this to be bypassed by commenting out the following “href” attribute:  
href=“system/launch/client/\<project\_name\>.jnlp”

Is this something that can be included in the next Ignition release?

Thanks,  
Jeremy Kiffer

 ![](https://us1.discourse-cdn.com/inductiveautomation/original/2X/8/8d63aaf6797b2811a726dc99343b034383853e17.jpg)

---

<div class="post-metadata">

**Author:** ![Carl.Gould](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/carl.gould/32/7262_2.png) [@Carl.Gould](https://forum.inductiveautomation.com/u/Carl.Gould)\
**Post date:** [June 23, 2015, 3:48pm UTC](https://forum.inductiveautomation.com/t/java-8-security-warnings-launching-clients-designer/10161/2 "2015-06-23T15:48:55Z")

</div>

Interesting, I didn’t realize that the href attribute was optional. We’ll have to do some research to see what the consequences of removing that attribute are. I imagine it would prevent the JWS system from re-downloading the JNLP to check for changes/updates, but we change that file so infrequently it may be a good trade-off.