Bug 191778

Summary:	Unavailable Critical Extension when trying to chain AD
Product:	[Retired] 389	Reporter:	Edward Patterson <edwpatterson>
Component:	Database - General	Assignee:	Noriko Hosoi <nhosoi>
Status:	CLOSED NOTABUG	QA Contact:	Orla Hegarty <ohegarty>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	1.0	CC:	ohegarty
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-05-17 14:38:53 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 Edward Patterson 2006-05-15 18:28:59 UTC

Description of problem:
Receive "Unavailable Critical Extension" when trying to chain to Active
Directory database.  Appears to involve the "Critical" LDAP control
2.16.840.1.113730.3.4.12 in the chained search query.

Version-Release number of selected component (if applicable):
1.0.2

How reproducible:
Consistent

Steps to Reproduce:
1. Create database link to an Active Directory LDAP source
2. Query
3.
  
Actual results:
Unavailable critical extension

Expected results:
Data

Additional info:

Comment 1 Edward Patterson 2006-05-17 14:40:16 UTC

Sorry for the post.  As I have done more research this appears to be an AD
issue, not a DS issue.

Comment 2 Chandrasekar Kannan 2008-08-11 23:46:52 UTC

Bug already CLOSED. setting screened+ flag