Bug 1145378

Summary:	Adding an entry with an invalid password as rootDN is incorrectly rejected
Product:	Red Hat Enterprise Linux 7	Reporter:	Noriko Hosoi <nhosoi>
Component:	389-ds-base	Assignee:	Noriko Hosoi <nhosoi>
Status:	CLOSED ERRATA	QA Contact:	Viktor Ashirov <vashirov>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	7.0	CC:	amsharma, mreynolds, nkinder, rmeggins
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	389-ds-base-1.3.4.0-1.el7	Doc Type:	Bug Fix
Doc Text:	Root DN (Directory Manager) and password administrators should bypass all password restrictions and syntax checks, but the checks were incorrectly applied. The bug was fixed and Root DN and password administrators have no restrictions.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-11-19 11:42:05 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Noriko Hosoi 2014-09-23 01:03:21 UTC

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/47900

root DN, aka "cn=directory manager", should not be restricted by password policy.  During ADD operations the root DN is incorrectly restricted by password policy.  Updating an existing entry, doing a MOD, works as expected.

Comment 1 mreynolds 2014-09-30 19:20:43 UTC

Fixed upstream.

Comment 2 Noriko Hosoi 2015-02-20 00:37:22 UTC

Test case: dirsrvtests/tickets/ticket47900_test.py

Comment 4 Amita Sharma 2015-08-28 07:35:38 UTC

INFO:ticket47900_test:Testcase PASSED
PASSED

========================================== 2 passed in 39.84 seconds ===========================================
wrote pytestdebug information to /export/ds/dirsrvtests/tickets/pytestdebug.log

Hence marking as VERIFIED

Comment 5 errata-xmlrpc 2015-11-19 11:42:05 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2015-2351.html