Java Security Access Control Exception
What will I need to do to get my application to run? Apart from rolling back versioning.
I am opening up an application that we access via Internet Explorer. The following error appears -
Connect failed
Exception: java.security.AccessContro
On Windows 7 machine I am utilizing Java 8_45 and running Internet Explorer 11.
I am opening up an application that we access via Internet Explorer. The following error appears -
Connect failed
Exception: java.security.AccessContro
On Windows 7 machine I am utilizing Java 8_45 and running Internet Explorer 11.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Well i'm assuming this is some kind of Java Web Start app (or even an applet, though you use the word 'application') - is that right?
ASKER
I believe it is a Java Applet that kicks off when logging in. So If I am to sign it, what would that entail?
More questions first: is it just for you that you're concerned or does it run for others too?
ASKER
This is everyone. We have not upgraded past Java 6_45 or IE9 for this exact reason.
I would like to see if I can get past this error without staying on the older version of IE and Java.
I would like to see if I can get past this error without staying on the older version of IE and Java.
Well then the proper way to ensure problem-free execution is to sign it. It could be the easiest way too, but there are possibly ways to relax the security policy through Group Policy in Windows, but that's not my field unfortunately.
Because of serious security holes in the JVM (and it should go without saying that your current [older] version is vulnerable), Oracle has now tightened up security to a very high level so that only code signed with a proper CA-certified certificate is deemed safe. Needless to say, it is the really the responsibility of the provider of the app to do that, not the user.
Because of serious security holes in the JVM (and it should go without saying that your current [older] version is vulnerable), Oracle has now tightened up security to a very high level so that only code signed with a proper CA-certified certificate is deemed safe. Needless to say, it is the really the responsibility of the provider of the app to do that, not the user.
ASKER
We simply went back to our vendor and they had loaded the most recent JAR file that had been tested with Java 8_45. Up to this point it had not been updated. Glad it worked! Thank-you.
ASKER