United StatesChange Country, Oracle Worldwide Web Sites Communities I am a... I want to...
Bug ID: JDK-8020390 LSP: LocalSecurityPolicy is initialized too soon
JDK-8020390 : LSP: LocalSecurityPolicy is initialized too soon

Details
Type:
Bug
Submit Date:
2013-07-11
Status:
Closed
Updated Date:
2014-02-12
Project Name:
JDK
Resolved Date:
2013-07-13
Component:
deploy
OS:
Sub-Component:
CPU:
Priority:
P2
Resolution:
Fixed
Affected Versions:
7u40
Fixed Versions:
7u40 (b34)

Related Reports
Backport:
Backport:
Backport:
Backport:
Duplicate:

Sub Tasks

Description
The initialization of LSP occurs too soon in both javaws and plugin causing lots of problems:
1.) it is initialized before proxies are initialized, so if it is valid policy jar with re vocation checking on, cannot use proxies to reach the OCSP.
2.) it is initialized before trace is initialized, so we cannot see Trace statements related to parsing lsp file.
3.) it is initialized in javaws when launch javaws for reasons other than running an app:
javaws -viewer, javaws -import, javaws - SSVBaselineUpdate, etc.
in all the above cases, revocation checking of a valid policy file may have to timeout before the operation can proceed.

                                    

Comments
move the call to LocalSecurityPolicy.initialize to later in the init sequence.
                                     
2013-07-11
SQE-OK to get this issue fixed in 7u40.
                                     
2013-07-12
Verified using 7u40-b42
                                     
2013-09-09



Hardware and Software, Engineered to Work Together