Launch client jar invalid

Ignition 8.3 Early Access
1

Testing Ignition 8.3.0 Beta. I had to upgrade my Designer Launcher to 1.3.0 Beta-1 to access the 8.3 designer.

However, I'm now unable to open any of my other 8.1.23 designers; I receive a "Launch client jar invalid" message. I ended up downgrading my designer, but this means I can no longer access 8.3. Has anyone else encountered this issue?

2

You'd probably be seeing the same issue if you upgraded to 8.1.34 or later, when the launchclient.jar code signing verification was introduced.

i.e. I don't think this an 8.3 specific issue, but rather something about your environment causing this verification to fail.

You probably need to set aside some time to upgrade to the latest 8.1.x release and then, if you are seeing this issue as I suspect you will, work with support to figure out why.

One cause for this I've seen is corporate firewall/MITM software modifying the JAR as its downloaded. Another can be some kind of error contacting OCSP endpoints. Hard to say without launching the designer from a command line and looking at the logs.

3

Ok, never mind what I said above. That's not what is happening here.

I can also reproduce this trying to use the 8.3 launcher against a pre-codesigning version of Ignition.

1 Like
4

Edit ~/.ignition/clientlauncher-data/designer-launcher.json, find the "signature.verification.strength" key, then set the value to "LENIENT".

...
"signature.verification.strength": "LENIENT",
...

Then you should get a prompt to trust the unsigned launcher JAR file when you launch against an older Gateway.

1 Like
5

Looks like this did get a section in the User Manual. The 8.3 manual does specifically mention 8.1.33 and older not working with the default of MODERATE. In the 8.1 launchers the default was set to LENIENT

8.1 Docs

8.3 Docs

6

Same issue. Try to change the parameter of .son file to LENIENT but when i restart the Designer Launcher it automatically roll back the parameter to MODERATE.

  • How can i fix it?

Thanks

7

Try closing the Designer Launcher first and then change the value to LENIENT

2 Likes
8

I will say that in order to take advantage of the signature verification, all 8.1 gateways should be upgraded to 8.1.34+ (Also for best compatibility with future upgrades to 8.3). Then by default Designers and Clients can be launched from 8.3 launchers.

As always, before upgrading make sure to take a gateway backup. It's also advisable to test any upgrades in a development environment first.

1 Like
9

You're right, it works.

Thanks

1 Like
10

Thank you for the response. Yes, we are planning to upgrade to 8.1.48 in the next few months. Just have to do it across all our 15 gateways to keep them consistent.

11

Awesome. That worked! Thank you very much for your help!