Bug 1023084
Summary: | [GSS] (6.3.0) Bug in JBossJSSESecurityDomain.java - attempting to use wrong provider | |||
---|---|---|---|---|
Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Derek Horton <dehort> | |
Component: | Security | Assignee: | Anil Saldhana <anil.saldhana> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Josef Cacek <jcacek> | |
Severity: | unspecified | Docs Contact: | Russell Dickenson <rdickens> | |
Priority: | unspecified | |||
Version: | 6.1.1 | CC: | bmaxwell, cdewolf, dehort, hmlnarik, smumford, twells | |
Target Milestone: | ER4 | |||
Target Release: | EAP 6.3.0 | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
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`.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1067574 (view as bug list) | Environment: | ||
Last Closed: | 2014-06-28 15:53:46 UTC | Type: | Bug | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1067574, 1067584 |
Description
Derek Horton
2013-10-24 15:08:01 UTC
Fixed. Checked into: https://svn.jboss.org/repos/picketbox/branches/eap62 Included release note text from duplicate bug 1067574. Marking for inclusion in 6.3.0 Release Notes. Fixed in 4.0.19.SP6 which based on 1088897 should be used in 6.3.0. Verified in EAP 6.3.0.ER4 As per bz 1097167, this has been set back to known issue. I removed the doc text so here it is, ready to be reinstated: 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`. Reinstated doc text. Making public for inclusion in 6.3.0 Release Notes. |