Posted on 01-16-2014 06:52 AM
Previously, we'd had trouble with our Cisco Tokenless VPN- https://jamfnation.jamfsoftware.com/discussion.html?id=9430
When Java 1.7.0_51 came out the other day, it messed everything up again (sigh). Never fear! Our team of tireless tyrannical techies never quits. It's a pretty simple fix, this time with a policy instead of a configuration profile.
In System Preferences, the new update shows a new window in the security tab:
You can simply add in your sites there, but if you want to roll something out for everyone, create a file with something like TextWrangler called "exception.sites".
Create a package in Composer where this file is put into ~/Library/Application Support/Oracle/Java/Deployment/security. This can be distributed via policy.
This, in tandem with the Safari plist configuration profile, makes it simple to accommodate when customers update java. We also created a combo updater that updates java, and adds the site list- that way people can get it all in one click of Self Service.
-ben
Posted on 01-16-2014 07:28 AM
Do you mean 1.7.0_51? That is the most recent version i'm seeing and I keep getting freaked out when I see this post :)
Posted on 01-16-2014 07:34 AM
I had to check myself once I saw that. I thought Oracle was severely speeding up their release cycle. LOL
Posted on 01-16-2014 07:38 AM
Sorry, yes, thanks for the catch.
Posted on 01-16-2014 07:47 AM
I've written a script for managing Oracle's new whitelist. For those interested, I have a post on it here:
http://derflounder.wordpress.com/2014/01/16/managing-oracles-java-exception-site-list