Problem browsing LDAP with Outlook
by Chris Bryant
When configuring Microsoft Outlook (not Outlook Express) to access an LDAP directory, there is an option to 'Enable Browsing (requires server support)'. If this option is chosen and the directory server supports it, then you should be able to open the LDAP address book and page up and down through the results. I have been unable to get this working properly with 389 DS.
When I try to browse from Outlook against the 389 DS directory, I am able to see the first page of results perfectly. However, if I move to the next page, only the first object returned will have any attributes included, and all of the rest of the objects in the page will have no attributes. I have a test perl script that duplicates this functionality as well.
I can get this to work properly with an older version of Netscape Directory Server, and I can get it working with OpenDS. Since 389 DS advertises support for the controls that are required for this to work, just like the other two servers, then I would expect it to work there also.
Has anyone out there gotten this to work with 389 DS? If so, can you share if there was anything special that you needed to do to get this to work? I'm trying to determine if this is a bug in the server, or if I'm just missing something in the configuration.
Thanks,
Chris
USA.NET
You Run Your Business. We'll Run Your Email.
This message is for the sole use of the intended recipient(s) and may contain confidential and/or privileged information of USA.NET, Inc. Any unauthorized review, use, copying, disclosure, or distribution is prohibited. If you are not the intended recipient, please immediately contact the sender by reply email and delete all copies of the original message.
3 years, 9 months
MemberOf group restrictions to a client system (server and client running CentOS 7)
by Janet Houser
Hi,
I'm new to 389-ds and last week downloaded and installed the software.
I have a running instance of the server, and I've added TLS/SSL. I've configured a CentOS 7 client to be able to query
the server using TLS/SSL, and all appears working.
I've created users and groups on the 389-ds server successfully. For each user and group, I've enabled posix attributes and my client
can see the unix users and groups using the "getent password" or "getent group" commands.
Now, here's where I'm getting tripped up..........
I need to limit which users have access to which systems. I've been trying to do this via memberOf group limitations.
I found the following online resource (https://thornelabs.net/2013/01/28/aix-restrict-server-login-via-ldap-grou...)
which is close enough to CentOS that the initial commands worked.
I enabled the MemberOf plugin and changed the attributes per the link, and restarted the system.
I created a test group (that I didn't enable a posix GID) and tried to add a single user via:
Right click on group -- > click Properties --> then Members --> click Add --> Search for user --> click Add.
When I try to go this route (which worked before enabling the memberOf plugin) it worked. Now it seems I get the error:
"Cannot save to directory server.
netscape.ldap.LDAPException: error resiult(65): Object class violation"
And the messages file throws the error (/var/log/dirsrv/slapd-<instancename>/errors:
"Entry "uid=test,ou=People,dc=int,dc=com" -- attribute "memberOf" not allowed
[17/Feb/2016:11:22:58 -0700] memberof-plugin - memberof_postop_modify: failed to add dn (cn=testgroup,ou=Groups,dc=int,dc=com) to target. Error (65)"
So it seems my server isn't quite using the memberOf plugin properly, but I'm not sure what else to enable. I'll have to solve this issue before
I even try to filter login access via groups on my client system.
I should mention that if I go under the advanced tab for one of the groups I created, I can add the the attribute "uniquemember", but I'm not sure what I
should set the "value" to be.
I've tried creating new users to see if I could set their "uniquemember" attributes, but no luck. It seems that I don't have the ability to set this attribute
on individual users, only groups.
This might not be the right road to head down when trying to restrict access to servers via groups, so I'm open to any suggestions.
Any suggestions would be appreciated.
3 years, 10 months
error moving an user
by Alberto Viana
Hey Guys,
389 version: 389-Directory/1.3.7.4.20170912git26a9426 B2017.255.1330
I'm trying to move one of my users to another OU and I see this kind of
error:
Error while moving entry
- [LDAP: error code 1 - Operations Error]
java.lang.Exception: [LDAP: error code 1 - Operations Error]
at
In the log I see:
[20/Mar/2018:14:12:27.172553808 -0300] - ERR - ldbm_back_modrdn -
SLAPI_PLUGIN_BE_TXN_POST_MODRDN_FN plugin returned error but did not set
SLAPI_RESULT_CODE
I thought that was related to my windows replication, but I disabled it and
I'm still getting the error.
Any clues?
5 years, 8 months
Replication Delay
by Fong, Trevor
Hi Everyone,
I’ve set up a new 389 DS cluster (389-Directory/1.3.6.1 B2018.016.1710) and have set up a replication agreement from our old cluster (389-Directory/1.2.11.15 B2014.300.2010) to a master node in the new cluster. Problem is that updates in the old cluster take up to 15 mins to make it into the new cluster. We need it to be near instantaneous, like it normally is. Any ideas what I can check?
Thanks a lot,
Trev
_________________________________________________
Trevor Fong
Senior Programmer Analyst
Information Technology | Engage. Envision. Enable.
The University of British Columbia
trevor.fong(a)ubc.ca<mailto:trevor.fong@ubc.ca> | 1-604-827-5247<tel:604-827-5247> | it.ubc.ca<http://it.ubc.ca>
6 years, 1 month
ldapsearch doesn't return the userpassword field
by Janet Houser
Hi,
I've been looking through the archives for information, but I haven't stumbled on a solution to my problem.
I'm running ds-389 (389-ds-base-1.3.4.0) on a centos 7 box (CentOS Linux release 7.2.1511). I have a centos OS client configured using SSL/TLS
which queries the LDAP server. Per a previous thread, I configured the memeberOf plugin and all seems to be working properly.
I have a php script that will run on the client and change the LDAP password for the user. The problem is, the script looks for the SSHA has
of the password when an ldapsearch is issued.
However, when I issue a general ldapsearch (anonymously) I don't get the userpassword field. I read in your archives that I might have
to be the "directory manager" user in order to see the hashed password. I've been playing around with the ldapsearch syntax, but I can't
quite get it right.
Anyway, my question is, can I set a flag in 389-ds that will display the hashed userpassword? I think that will solve my problem with the php script returning an error that it can't retrieve the old password.
Thanks,
6 years, 1 month
ns-slapd segfault
by Bart
Hi all,
I am using 389-ds as a part of FreeIPA setup. I've established trust with AD domain but ds server crashes when I try to authenticate with an AD user on a linux system.
The version I am using is:
389-ds-base.x86_64 1.3.7.10-1.fc27 @updates
389-ds-base-libs.x86_64 1.3.7.10-1.fc27 @updates
Related dmesg output is:
[ 2998.558825] ns-slapd[1019]: segfault at 0 ip 00007f5cfa4aa20b sp 00007f5cca64fab0 error 4 in libtcmalloc.so.4.4.5[7f5cfa483000+46000]
[69484.585785] ns-slapd[5558]: segfault at 0 ip 00007ff7a797620b sp 00007ff773e9dab0 error 4 in libtcmalloc.so.4.4.5[7ff7a794f000+46000]
[70128.856460] ns-slapd[5799]: segfault at 0 ip 00007f5bb28e820b sp 00007f5b83e19cd0 error 4 in libtcmalloc.so.4.4.5[7f5bb28c1000+46000]
[70841.531994] ns-slapd[6687]: segfault at 0 ip 00007f3b26217213 sp 00007f3af9b84b00 error 4 in libtcmalloc.so.4.4.5[7f3b261f0000+46000]
Everything runs on Fedora 27, I use the packages from the upstream repo.
Can anyone point me to the way of fixing this?
Thank you
Bart
6 years, 1 month
Experiences with Large Groups (>100k Members)
by Fong, Trevor
Hi Everyone,
I was wondering what experiences people have had with large groups (> 100k members) in 389 DS?
Particularly interested in loading, managing and syncing them.
WRT syncing – how do people efficiently sync large groups? Most sync utilities sync at the attribute level; if the changed attribute (eg member) is multivalued, it just replaces all values. That’s OK if there’s only a few values, but is not efficient when there are a large number of them. A more efficient way would be to diff the 2 attributes and add/delete the differences; does anyone know of any sync tools that do something like this?
Background:
I have a few particularly large groups of > 500k members that are currently handled in a DBMS, but want to migrate them to LDAP instead.
When I try to load them via ldapmodify, doing an add:member per member was going to take more than 24 hrs at rate of processing at the time of abort.
Trying to add all members instead, with a single add:member and listing all members after that instruction, eventually ended with an Operations Error. Turning on housekeeping error level showed it was getting “Lock table is out of available lock entries” error – I’m in the process of retrying with adjusted nsslapd-db-locks in cn=config,cn=ldbm database,cn=plugins,cn=config.
Thanks,
Trev
_________________________________________________
Trevor Fong
Senior Programmer Analyst
Information Technology | Engage. Envision. Enable.
The University of British Columbia
trevor.fong(a)ubc.ca<mailto:trevor.fong@ubc.ca> | 1-604-827-5247<tel:604-827-5247> | it.ubc.ca<http://it.ubc.ca>
6 years, 1 month
Re: Experiences with Large Groups (>100k Members)
by Fong, Trevor
Just an update:
I was successful in loading 532k members into a group, in ~45 mins, via ldapmodify by segmenting the ldif into 5 separate add:member sections, of ~100k each. I also set nsslapd-db-locks in cn=config,cn=ldbm database,cn=plugins,cn=config to 400000 – not sure which made any difference.
Still interested in other people’s experience with large groups.
From: "Fong, Trevor" <trevor.fong(a)ubc.ca>
Reply-To: "389-users(a)lists.fedoraproject.org" <389-users(a)lists.fedoraproject.org>
Date: Thursday, April 26, 2018 at 11:06 AM
To: "389-users(a)lists.fedoraproject.org" <389-users(a)lists.fedoraproject.org>
Subject: [389-users] Experiences with Large Groups (>100k Members)
Hi Everyone,
I was wondering what experiences people have had with large groups (> 100k members) in 389 DS?
Particularly interested in loading, managing and syncing them.
WRT syncing – how do people efficiently sync large groups? Most sync utilities sync at the attribute level; if the changed attribute (eg member) is multivalued, it just replaces all values. That’s OK if there’s only a few values, but is not efficient when there are a large number of them. A more efficient way would be to diff the 2 attributes and add/delete the differences; does anyone know of any sync tools that do something like this?
Background:
I have a few particularly large groups of > 500k members that are currently handled in a DBMS, but want to migrate them to LDAP instead.
When I try to load them via ldapmodify, doing an add:member per member was going to take more than 24 hrs at rate of processing at the time of abort.
Trying to add all members instead, with a single add:member and listing all members after that instruction, eventually ended with an Operations Error. Turning on housekeeping error level showed it was getting “Lock table is out of available lock entries” error – I’m in the process of retrying with adjusted nsslapd-db-locks in cn=config,cn=ldbm database,cn=plugins,cn=config.
Thanks,
Trev
_________________________________________________
Trevor Fong
Senior Programmer Analyst
Information Technology | Engage. Envision. Enable.
The University of British Columbia
trevor.fong(a)ubc.ca<mailto:trevor.fong@ubc.ca> | 1-604-827-5247<tel:604-827-5247> | it.ubc.ca<http://it.ubc.ca>
6 years, 1 month
Announcing 389 Directory Server 1.4.0.8
by Mark Reynolds
389 Directory Server 1.4.0.8
The 389 Directory Server team is proud to announce 389-ds-base
version 1.4.0.8
Fedora packages are available on Fedora 28 and 29(rawhide).
Rawhide(F29)
https://koji.fedoraproject.org/koji/taskinfo?taskID=26461258
<https://koji.fedoraproject.org/koji/taskinfo?taskID=26461258>
F28
https://koji.fedoraproject.org/koji/taskinfo?taskID=26461070
<https://koji.fedoraproject.org/koji/taskinfo?taskID=26461070>
https://bodhi.fedoraproject.org/updates/FEDORA-2018-f36db5c2bf
<https://bodhi.fedoraproject.org/updates/FEDORA-2018-f36db5c2bf>
The new packages and versions are:
* 389-ds-base-1.4.0.8-1
Source tarballs are available for download at Download
389-ds-base Source
<https://releases.pagure.org/389-ds-base/389-ds-base-1.4.0.8.tar.bz2>
Highlights in 1.4.0.8
* Bug fixes
Installation and Upgrade
See Download <http://www.port389.org/docs/389ds/download.html> for
information about setting up your yum repositories.
To install, use *yum install 389-ds* yum install 389-ds After install
completes, run *setup-ds-admin.pl* if you have 389-admin installed,
otherwise please run *setup-ds.pl* to set up your directory server.
To upgrade, use *yum upgrade* yum upgrade After upgrade completes, run
*setup-ds-admin.pl -u* if you have 389-admin installed, otherwise please
run *setup-ds.pl* to update your directory server/admin
server/console information.
See Install_Guide
<http://www.port389.org/docs/389ds/legacy/install-guide.html> for more
information about the initial installation, setup, and upgrade
See Source <http://www.port389.org/docs/389ds/development/source.html>
for information about source tarballs and SCM (git) access.
Feedback
We are very interested in your feedback!
Please provide feedback and comments to the 389-users mailing list:
https://lists.fedoraproject.org/admin/lists/389-users.lists.fedoraproject...
If you find a bug, or would like to see a new feature, file it in our
Pagure project: https://pagure.io/389-ds-base
* Bump version to 1.4.0.8
* Ticket 49639 - Crash when failing to read from SASL conn
* Ticket 49109 - nsDS5ReplicaTransportInfo should accept StartTLS as
an option
* Ticket 49586 - Add py3 support to plugins test suite
* Ticket 49511 - memory leak in pwdhash
6 years, 2 months
Enabling TLS in Directory Server Using the Console
by Jeremy Tourville
I am following the Red Hat Directory Server 10 Admin Guide under section 9.4.1.2. So far I have been able to create the certificates and database and getting the certs imported to the proper locations. My issue happens when I attempt to restart the services. The service eventually just times out trying to restart and I get a message "the server could not be restarted". I end up losing the changes I had just made in the console. I have tried to review my settings to be sure I didn't overlook something and everything seems to be ok. What logs should I be reviewing to see why the service isn't restarting properly?
6 years, 2 months
