-
Bug
-
Resolution: Fixed
-
P2
-
None
-
b38
Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8023040 | 7u60 | Unassigned | P2 | Resolved | Fixed | b01 |
JDK-8022715 | 7u51 | Unassigned | P2 | Resolved | Fixed | b01 |
JDK-8022565 | 7u45 | Unassigned | P2 | Resolved | Fixed | b06 |
A new deployment property has been added in 7u40 to allow customers that manage their own Java updates to avoid having users prompted with the "Insecure JRE" warning message.
Background: When the installed JRE, 7u10 or later, falls below the security baseline OR passes it's built-in expiration date an additional warning is show to users to prompt them to update their installed JRE to the latest version. For businesses that manage the update process this may cause problems when users attempt to update their JRE themselves.
To suppress this one specific warning message add the following in the deployment properties file:
deployment.expiration.check.enabled=false
(this should be updated both in the release notes and in the deployment guide where deployment properties are documented)
Background: When the installed JRE, 7u10 or later, falls below the security baseline OR passes it's built-in expiration date an additional warning is show to users to prompt them to update their installed JRE to the latest version. For businesses that manage the update process this may cause problems when users attempt to update their JRE themselves.
To suppress this one specific warning message add the following in the deployment properties file:
deployment.expiration.check.enabled=false
(this should be updated both in the release notes and in the deployment guide where deployment properties are documented)
- backported by
-
JDK-8022565 document the use of deployment.expiration.check.enabled
-
- Resolved
-
-
JDK-8022715 document the use of deployment.expiration.check.enabled
-
- Resolved
-
-
JDK-8023040 document the use of deployment.expiration.check.enabled
-
- Resolved
-