Back to bug 1023084
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Derek Horton | 2014-01-14 21:13:12 UTC | Target Release | --- | EAP 6.2.2 |
| Blocks | 1049365 | |||
| Derek Horton | 2014-01-16 20:39:01 UTC | Link ID | JBoss Issue Tracker SECURITY-762 | |
| Carlo de Wolf | 2014-02-11 08:04:48 UTC | Target Release | EAP 6.2.2 | EAP 6.3.0 |
| CC | cdewolf | |||
| Blocks | 1049365 | |||
| Derek Horton | 2014-02-20 16:33:22 UTC | Summary | Bug in JBossJSSESecurityDomain.java - attempting to use wrong provider | [GSS] (6.3.0) Bug in JBossJSSESecurityDomain.java - attempting to use wrong provider |
| Derek Horton | 2014-02-20 16:34:33 UTC | Blocks | 1067574 | |
| Derek Horton | 2014-02-20 16:48:40 UTC | Status | NEW | POST |
| Derek Horton | 2014-02-20 16:49:47 UTC | Blocks | 1067584 | |
| Brad Maxwell | 2014-02-24 06:00:30 UTC | CC | bmaxwell | |
| Scott Mumford | 2014-05-13 02:43:41 UTC | CC | smumford | |
| Doc Text | Previous versions of JBoss EAP 6 included a bug which caused JBossJSSESecurityDomain.java to attempt to use the keystore/truststore provider to get instances of the trust manager. This behavior was incorrect as the "trust-manager-factory-provider" setting cannot be used in the JSSE section of a security domain. Using this setting (even if properly configured) would result in an exception during start up. This bug has been resolved in this release and the "trust-manager-factory-provider" setting can now be used to set the trustManagerFactoryProvider. | |||
| Tom WELLS | 2014-05-14 02:08:17 UTC | CC | dehort, twells | |
| Flags | needinfo?(dehort) | |||
| Derek Horton | 2014-05-14 13:52:36 UTC | Flags | needinfo?(dehort) | |
| Derek Horton | 2014-05-14 14:17:13 UTC | Status | POST | ON_QA |
| Target Milestone | --- | ER4 | ||
| Hynek Mlnarik | 2014-05-14 15:00:11 UTC | Status | ON_QA | VERIFIED |
| CC | hmlnarik | |||
| Nichola Moore | 2014-05-15 04:57:23 UTC | CC | nmoore | |
| Doc Text | Previous versions of JBoss EAP 6 included a bug which caused JBossJSSESecurityDomain.java to attempt to use the keystore/truststore provider to get instances of the trust manager. This behavior was incorrect as the "trust-manager-factory-provider" setting cannot be used in the JSSE section of a security domain. Using this setting (even if properly configured) would result in an exception during start up. This bug has been resolved in this release and the "trust-manager-factory-provider" setting can now be used to set the trustManagerFactoryProvider. | doc text in comment 9 | ||
| Doc Type | Bug Fix | Known Issue | ||
| Nichola Moore | 2014-05-15 04:58:28 UTC | Doc Text | doc text in comment 9 | Previous versions of JBoss EAP 6 included a bug which caused JBossJSSESecurityDomain.java to attempt to use the keystore/truststore provider to get instances of the trust manager. This behavior was incorrect as the "trust-manager-factory-provider" setting cannot be used in the JSSE section of a security domain. Using this setting (even if properly configured) would result in an exception during start up. This bug has been resolved in this release and the "trust-manager-factory-provider" setting can now be used to set the `trustManagerFactoryProvider`. |
| Scott Mumford | 2014-05-15 05:11:29 UTC | Doc Text | Previous versions of JBoss EAP 6 included a bug which caused JBossJSSESecurityDomain.java to attempt to use the keystore/truststore provider to get instances of the trust manager. This behavior was incorrect as the "trust-manager-factory-provider" setting cannot be used in the JSSE section of a security domain. Using this setting (even if properly configured) would result in an exception during start up. This bug has been resolved in this release and the "trust-manager-factory-provider" setting can now be used to set the `trustManagerFactoryProvider`. | This release of JBoss EAP 6 includes a bug which causes JBossJSSESecurityDomain.java to attempt to use the keystore/truststore provider to get instances of the trust manager. This behavior is incorrect as the "trust-manager-factory-provider" setting cannot be used in the JSSE section of a security domain. Using this setting (even if properly configured) will result in an exception during start up. This issue is will be resolved in a future release of the product. |
| Tom WELLS | 2014-05-15 09:20:46 UTC | Doc Text | This release of JBoss EAP 6 includes a bug which causes JBossJSSESecurityDomain.java to attempt to use the keystore/truststore provider to get instances of the trust manager. This behavior is incorrect as the "trust-manager-factory-provider" setting cannot be used in the JSSE section of a security domain. Using this setting (even if properly configured) will result in an exception during start up. This issue is will be resolved in a future release of the product. | Previous versions of JBoss EAP 6 included a bug which caused JBossJSSESecurityDomain.java to attempt to use the keystore/truststore provider to get instances of the trust manager. This behavior was incorrect as the "trust-manager-factory-provider" setting cannot be used in the JSSE section of a security domain. Using this setting (even if properly configured) would result in an exception during start up. This bug has been resolved in this release and the "trust-manager-factory-provider" setting can now be used to set the `trustManagerFactoryProvider`. |
| Doc Type | Known Issue | Bug Fix | ||
| mark yarborough | 2014-06-28 15:53:46 UTC | Status | VERIFIED | CLOSED |
| Resolution | --- | CURRENTRELEASE | ||
| Last Closed | 2014-06-28 11:53:46 UTC | |||
| Scott Mumford | 2014-07-17 04:11:24 UTC | Group | redhat, private | |
| Nichola Moore | 2014-08-12 02:08:52 UTC | CC | nmoore |
Back to bug 1023084