Bug 1133961

Summary: XML parsing mandating the 'force' attribute on username-to-dn even though it has a default value.
Product: [JBoss] JBoss Enterprise Application Platform 6 Reporter: Darran Lofthouse <darran.lofthouse>
Component: Domain ManagementAssignee: Darran Lofthouse <darran.lofthouse>
Status: CLOSED CURRENTRELEASE QA Contact: Petr Kremensky <pkremens>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.4.0CC: dandread, kkhan
Target Milestone: DR1   
Target Release: EAP 6.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
In JBoss EAP 6, where a `username-to-dn` element is defined for LDAP based authorization with security realms, the schema describes an optional attribute; `force`. In previous versions of the product the parser was implemented to assume this attribute was mandatory. This caused configurations which were valid according to the schema to be rejected by the parser if the optional attribute was omitted. In this release the parser has been updated to reflect the fact that the attribute is optional and configurations that omit the `force` attribute will now be correctly parsed by the parser.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2019-08-19 12:43:55 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:

Description Darran Lofthouse 2014-08-26 14:30:38 UTC 
Description of problem:

The changes for EAP6-191 are bringing the bulk of the security realm implementation in-line with upstream - this is good as it simplifies future ports from WildFly to EAP - however there are a couple of bug fixes implemented upstream only that should be backported, this is one of them.

The schema definition for username-to-dn contains an attribute 'force' with a default value defined - the XML parser however is assuming this attribute is required and throwing an exception if it is omitted from the configuration.
Comment 2 Petr Kremensky 2014-09-22 06:47:32 UTC 
Verified on EAP 6.4.0.DR1.1