Thread: Java Security Issue(s)

Problem #1 means you just need to set the codebase attribute in the manifest and JNLP page. That's not bad. The codebase just should be the website domain name.

Problem #2 is where it gets bad. The Java 7 Version 51 update a week ago has made it so unsigned and self-signed applets refuse to start. One solution is purchasing a certificate. But another solution is to instruct your user to add your website to their exception list. The error message about the application to resources across multiple domains is probably related to you not having Problem #1 resolved.

For problem#2 I assume that the website was created by someone else. Can you contact the author about the problem?
A project I thought of for those problems is a stripped down browser written in java that would read the html page, parse out the <APPLET tag, read the jar file and execute the applet code without any security problems.

I have a website that has an applet that is still working for me. It gives warnings, but allows the applet to execute.
Way Points

Is the website in your Exception Site List? If not, that would be the reason. It might not be your browser security settings blocking it, but your java security settings.

Originally Posted by Jim Corner

Thanks Norm, but when I clicked on the "Activate Java Platform" pop up I get this error message (the same one I see with Chess.com) - "Your security settings have blocked an untrusted application from running". This baffles me because my browser security setting is medium, where the browser is supposed to ask me if I want to run the app, and then run it when I say yes. I don't know if it will help, but here are the error details:

Java Plug-in 10.51.2.13
Using JRE version 1.7.0_51-b13 Java HotSpot(TM) Client VM
User home directory = C:\Users\robert barnes
----------------------------------------------------
c: clear console window
f: finalize objects on finalization queue
g: garbage collect
h: display this help message
l: dump classloader list
m: print memory usage
o: trigger logging
q: hide console
r: reload policy configuration
s: dump system and deployment properties
t: dump thread list
v: dump thread stack
x: clear classloader cache
0-5: set trace level to <n>
----------------------------------------------------

This isn't an error, it's just the default text that pops up in the Java console.

I wrote a tutorial on changing your security settings here: Deployment - Tutorials - Static Void Games