Bug 1133961 – XML parsing mandating the 'force' attribute on username-to-dn even though it has a default value.

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

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 ...

Status:	VERIFIED

Aliases:	None

Product:	JBoss Enterprise Application Platform 6
Classification:	JBoss
Component:	Domain Management (Show other bugs)
Sub Component:
Version:	6.4.0
Hardware:	Unspecified Unspecified

Priority	unspecified Severity medium
Target Milestone:	DR1
Target Release:	EAP 6.4.0
Assigned To:	Darran Lofthouse
QA Contact:	Petr Kremensky
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2014-08-26 10:30 EDT by Darran Lofthouse
Modified:	2018-03-06 15:39 EST (History)
CC List:	2 users (show)

See Also:
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:
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
JBoss Issue Tracker	WFLY-3269	Major	Closed	XML parsing mandating the 'force' attribute on username-to-dn even though it has a default value.	2018-09-04 13:29 EDT

Groups: None (edit)

Description Darran Lofthouse 2014-08-26 10:30:38 EDT

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 02:47:32 EDT

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.