JDK-8049518 : Security Level are not Very High after reinstalling JRE with "WEB_JAVA_SECURITY_LEVEL=VH"
  • Type: Bug
  • Component: install
  • Affected Version: 8u20
  • Priority: P2
  • Status: Closed
  • Resolution: Duplicate
  • Submitted: 2014-07-08
  • Updated: 2014-07-09
  • Resolved: 2014-07-09
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.
JDK 8
8u20Resolved
Related Reports
Duplicate :  
JDK-8049056 - Deployment .jar files are missing in JAVA_HOME\lib, when installer calls RegisterDeployEx() from deploy.dll
Description
The issue is reproducible on windows vista x86.
The issue is found since 8u20 b19, it is good with and before 8u20b18.
To reproduce:
1.Login with adminstrator prevelidge on a clean system
2.Install JRE via command line installer, provide no args
3.Add the following line into system level deployment file
deployment.security.level=HIGH
make sure it's locked - add key deployment.security.level.locked in the same file.
4.Uninstall the JRE.
5.Reinstall the JRE via command line installer, provide args args to set Security Level to Very High: "jre_installer.exe WEB_JAVA_SECURITY_LEVEL=VH."
expected behavior:
After installation, open JCP, check Security Level is set to Very High and still locked.

The actual result:
Security Level can't be set to Very High after reinstalling JRE:"jre_installer.exe WEB_JAVA_SECURITY_LEVEL=VH."
Comments
I believe this is a duplicate of 8049056. The issue is the deploy.jar wasn't there during the RegisterDeploy call.
09-07-2014
The issue can be reproducible on win7 as well. Yes the security level locked in the JCP after step 5, so there is no manual workaround for the user to set security level to very high.
09-07-2014
Is this issue ONLY reproducible on Vista? Or is that simply the OS used when finding the bug? Is the security level locked in the JCP after step 5? So there is no manual workaround for the user to set security level to very high?
08-07-2014
Affected tests: installerArgsScenarios/testAdminInstallSecurityLevelOverrideLocked installerArgsScenarios/testAdminInstallSecurityLevelOverrideUnlocked installerArgsScenarios/testAdminReinstallSecurityLevelOverrideLocked installerArgsScenarios/testAdminReinstallSecurityLevelOverrideUnlocked installerArgsScenarios/testStdUserInstallSecurityLevelOverrideLocked installerArgsScenarios/testStdUserInstallSecurityLevelOverrideUnlocked installerArgsScenarios/testStdUserReinstallSecurityLevelOverrideLocked installerArgsScenarios/testStdUserReinstallSecurityLevelOverrideUnlocked
08-07-2014