Bug 1133961 - XML parsing mandating the 'force' attribute on username-to-dn even though it has a default value.
Summary: XML parsing mandating the 'force' attribute on username-to-dn even though it ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Domain Management
Version: 6.4.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: DR1
: EAP 6.4.0
Assignee: Darran Lofthouse
QA Contact: Petr Kremensky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-26 14:30 UTC by Darran Lofthouse
Modified: 2019-08-19 12:43 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2019-08-19 12:43:55 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker WFLY-3269 0 Major Closed XML parsing mandating the 'force' attribute on username-to-dn even though it has a default value. 2019-08-01 11:46:26 UTC

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
Note You need to log in before you can comment on or make changes to this bug.