389-ds-base

#48182 console throws err=12 when chaining to AD
Closed: wontfix by mreynolds. Opened by rmeggins.

Closed: wontfix
Reopen Issue

Set up a chaining db to AD - do not use proxy authentication

Try to use the console to view the suffix, you get this:
[08/May/2015:13:14:56 -0500] conn=1 op=133 SRCH base="dc=domain2,dc=com" scope=0 filter="(|(objectClass=*)(objectClass=ldapsubentry))" attrs="distinguishedName"
[08/May/2015:13:14:56 -0500] conn=1 op=133 RESULT err=12 tag=101 nentries=0 etime=0

I think it is passing the MTN control through to AD which doesn't like it. Not sure if we can fix it, but we might have to add this to the documentation about how to tell the console not to send this control, or configure the chaining not to pass this control to AD.

Metadata Update from @rmeggins:
- Issue set to the milestone: 1.3.6 backlog

Metadata Update from @mreynolds:
- Custom field component reset (from UI - Dir Browser)
- Issue close_status updated to: None
- Issue set to the milestone: 389-admin,console FUTURE (was: 1.3.6 backlog)

Admin server/Console is deprecated, closing ticket...

Metadata Update from @mreynolds:
- Custom field reviewstatus adjusted to None
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/1513

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.
Metadata
None
None
None
None
Normal
Community
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.