On January 14, 2014 a new update to the Java runtime was released (1.7.0_51). This release includes a major change in the way Java handles self-signed Java applications like Praisenter.
NOTE: This only affects users running the Webstart download.
The Problem
The update does not allow Praisenter to run unless you manually change your security settings in the Java Control Panel. You will see something like the following after the update:
The Workaround
To allow Praisenter to run you must do one of the following:
- Lower your security settings in the Java Control Panel.
- Add http://www.praisenter.org to the Exception Site List.
We recommend that you go with option 2 for the best security. This will allow Praisenter to run but will continue to block other self-signed Java applications.
To change either setting you need to go to the Java Control Panel. On Windows, you can either find it in Control Panel or just search for “Java”. On Mac OS X you can go to the Apple icon, System Preferences…, Java. Next click on the Security tab to see something similar to the following:
Click on the “Edit Site List” button. Next click the “Add” button. In the “Location” text box type http://www.praisenter.org. Then click the “Add” button. You should see something like the following when you clicked it:
Click “Continue” then click “Ok” until all the Java Control Panel windows are closed. You should be able to run Praisenter now.
More Discussion
At this point you might be wondering, “Why isn’t Praisenter signed properly” or something to that effect. Well, up until this update it really hasn’t been an issue. The only problem was users seeing a nasty warning message. Now, as you can see, things have changed and we need to re-evaluate this decision. The major factor in getting Praisenter signed properly is cost, as you might imagine.
Until a decision is made, the above steps will be necessary.
