#152 Directory Server should support LDAP aliases
Closed: wontfix 4 years ago by mreynolds. Opened 12 years ago by mkosek.

https://bugzilla.redhat.com/show_bug.cgi?id=178898

Description of problem:

The Fedora Directory Server does not honor alias dereferencing requests

Version-Release number of selected component (if applicable):
Fedora Directory Server 1.0.1


How reproducible:
An ldapsearch using the correct '-a' syntax

Steps to Reproduce:
# ldapsearch -a always -x -b
'uid=myuser,ou=Accounts,ou=Office,dc=company,dc=com' -s base -h
ns-slapd.company.com 'uid=myuser' 'uid'

dn: uid=myuser,ou=Accounts,ou=Office,dc=company,dc=com
uid: myuser

Expected results:
# ldapsearch -a always -x -b
'uid=myuser,ou=Accounts,ou=Office,dc=company,dc=com' -s base -h
openldap.company.com 'uid=myuser' 'uid'

dn: cn=My User,ou=Persons,ou=Office,dc=company,dc=com
uid: myuser

Additional info: using the openldap ldapsearch or fedora provided ldapsearch
from /opt/fedora-ds/shared/bin does not make a difference. The fedora ds server
does not honor the -a setting, nor any -a setting (find, search or always) and
handles it by the default -never setting.

batch update moving tickets to future

set default ticket origin to Community

Added initial screened field value.

Metadata Update from @nkinder:
- Issue set to the milestone: FUTURE

7 years ago

Does the 389 Directory Server still not support LDAP aliases?

Does the 389 Directory Server still not support LDAP aliases?

Correct, we still do not support aliases. There are no plans to add this functionality at this time.

Metadata Update from @mreynolds:
- Custom field reviewstatus adjusted to None (was: Needs Review)
- Issue close_status updated to: None

4 years ago

So you have been ignoring this feature since 2006? That's impressive :)

I have to assume that with 389 Directory Server there is another way to achieve the same or similar functionality as LDAP aliases do, right?

So you have been ignoring this feature since 2006? That's impressive :)

and looks like there was no real demand
it is an open source product, contributions are welcome :-)

I have to assume that with 389 Directory Server there is another way to achieve the same or similar functionality as LDAP aliases do, right?

we have smart referrals, which is probably not exactly what you want. But it could be a good starting point to manage aliases

Generally in these cases, I always ask "what are you trying to achieve". Sometimes there may be an easier or alternative method that doesn't involve new code/features.

Since there is no demand for this, we are going to close it out for now...

Metadata Update from @mreynolds:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

4 years ago

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/152

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.

Login to comment on this ticket.

Metadata