JDK-4303068 : Policy provider should be controllable from the command line
  • Type: Enhancement
  • Component: security-libs
  • Sub-Component: java.security
  • Affected Version: 1.2.2
  • Priority: P4
  • Status: Resolved
  • Resolution: Fixed
  • OS: generic
  • CPU: generic
  • Submitted: 2000-01-06
  • Updated: 2001-03-10
  • Resolved: 2001-03-10
The Version table provides details related to the release that this issue/RFE will be addressed.

Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.

To download the current JDK release, click here.
Other
1.4.0 betaFixed
Related Reports
Relates :  
Description
It should be possible to specify an alternate Policy provider on the java command line, rather than having to edit an SDK/JRE installation. The latter is not conducive to read-only and shared installations.

Comments
CONVERTED DATA BugTraq+ Release Management Values COMMIT TO FIX: generic FIXED IN: merlin-beta INTEGRATED IN: merlin-beta
14-06-2004

EVALUATION charlie.lai@Eng 2001-03-08 allowed the entire java.security properties file to be specified from the command line via the system property, java.security.properties=<URL>. this properties file appends to the system properties file. if both properties files specify values for the same key, the value from command-line properties file wins, as it is the last one loaded. also, if you specify java.security.properties==<URL> (2 equals), then that properties file completely overrides the system properties file. to disable the ability to specify an additional properties file from the command line, set the key security.overridePropertiesFile to false in the system properties file. it is set to true by default.
11-06-2004

PUBLIC COMMENTS It should be possible to specify an alternate Policy provider on the java command line, rather than having to edit an SDK/JRE installation. The latter is not conducive to read-only and shared installations.
10-06-2004