That breaks our product usage on Mac OS X Clients in standard settings with Gatekeeper enabled!
A solution would be a site based Gatekeeper configuration in Safari as it is already implemented for Java usage itself.
Reason: Our JNLP file is created dynamically on every application launch to insert a one-time-ticket to allow the client to authenticate after the user already authenticated himself on the application web page.
Technically we could enhance the Servlet creating the JNLP file by signing the output, but that would mean we needed to insert our secret developer signing key into our server application which is distributed to customers. And that is of course not possible if you don't want to find your secret key later anywhere on the Internet.
Am 05.06.2013 um 23:40 schrieb Steve Kann <email@hidden>:
> Just noticed this tidbit from 10.8.4 -- and have started hearing from some users about it.
> • Note: Starting with OS X v10.8.4, Java Web Start (i.e. JNLP) applications downloaded from the Internet need to be signed with a Developer ID certificate. Gatekeeper will check downloaded Java Web Start applications for a signature and block such applications from launching if they are not properly signed.
> Is there more documentation about this requirement available? Is an Apple Developer ID Certificate required, or will a normal Code Signing certificate (as used to sign .jar files) suffice?
> Was there any notice about this on these lists?
> Do not post admin requests to the list. They will be ignored.
> Java-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
> This email sent to email@hidden
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden