JDK-6945109 : Custom progress: signed progress cause extra security dialog
- Type: Bug
- Component: deploy
- Sub-Component: deployment_toolkit
- Affected Version: 6u18,6u21
- Priority: P2
- Status: Resolved
- Resolution: Fixed
- OS: generic
- CPU: generic
- Submitted: 2010-04-19
- Updated: 2010-09-17
- Resolved: 2010-05-28
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.
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 6 | JDK 7 |
|---|---|
6u21 b05Fixed  |
7Fixed |
Related Reports
|
Duplicate :
|
|
|
Relates :
|
|
|
Relates :
|
Description
Mixed code protection prohibits mixing signed and unsigned jars in the same JNLP. Therefore progress jars also need to be signed. However, even if signed with same certificate they seem to be validated independently of other jars, i.e. if certificate has never been permanently accepted then user will see 2 different dialogs requesting permissions for the same certificate.
Comments
|