389-users July 2018

389-users@lists.fedoraproject.org

9 participants
15 discussions

Problem browsing LDAP with Outlook
by Chris Bryant 26 Aug '20

26 Aug '20

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 2

MemberOf group restrictions to a client system (server and client running CentOS 7)
by Janet Houser 06 Aug '20

06 Aug '20

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-groups…) 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.

6 19

tls encryption and key changes: symmetric key failed to unwrap
by Jan Kowalsky 04 Feb '19

04 Feb '19

Hi all, we have the following situation: An 389ds with tls/ssl configured whith an certificate from letsencrypt. Since letsencrypt is short-dated we have an automated update routine for regenerating the cert8.db. Now we have this sort of errors in changelog. [01/Jun/2018:11:46:40 +0200] attrcrypt - attrcrypt_unwrap_key: failed to unwrap key for cipher AES [01/Jun/2018:11:46:40 +0200] attrcrypt - attrcrypt_cipher_init: symmetric key failed to unwrap with the private key; Cert might have been renewed since the key is wrapped. To recover the encrypted contents, keep the wrapped symmetric key value. [01/Jun/2018:11:46:40 +0200] attrcrypt - attrcrypt_unwrap_key: failed to unwrap key for cipher 3DES [01/Jun/2018:11:46:40 +0200] attrcrypt - attrcrypt_cipher_init: symmetric key failed to unwrap with the private key; Cert might have been renewed since the key is wrapped. To recover the encrypted contents, keep the wrapped symmetric key value. [01/Jun/2018:11:46:40 +0200] attrcrypt - All prepared ciphers are not available. Please disable attribute encryption. I never used attribute encryption and we don't need it at the moment. But as far as I understand, it's based on the server private key. This is the one we change every 60 days. The best idea seems to disable attribute encryption (which doesn't make much sense if the private key isn't password protected anyway). Or is there any other way to deal with key changes? Thanks and regards Jan

4 5

error moving an user
by Alberto Viana 09 Oct '18

09 Oct '18

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?

4 9

simple question: do I need an admin server at all ?
by Robert Watterson 08 Aug '18

08 Aug '18

Hi forgive the newbie question, but I've searched the 389-users archive and didn't see an answer..... If I manage ldap entries and dirsrv server options via command line only, do I even need an admin server component? I've been using Apache Directory Studio for my non-command line needs on a single 389 instance, seems to work out OK so far. The admin server (o=netscape) is installed and running, but I haven't been using the GUI. I'm about to spin up two new servers and do multi-master replication and certificates/TLS. On a production server where all content changes are done via scripts (no GUI needed) do I even need to spin up an admin server? We won't be using Admin Express, DS Gateway, Org Chart, etc. We'll never be managing more than 3-4 production ldap servers. Am I missing something critical by installing just the actual 389 servers and NOT the admin instance?

4 3

Announcing 389 Directory Server 1.3.8.6
by Mark Reynolds 20 Jul '18

20 Jul '18

389 Directory Server 1.3.8.6 The 389 Directory Server team is proud to announce 389-ds-base version 1.3.8.6 Fedora packages are available on Fedora 27. https://koji.fedoraproject.org/koji/taskinfo?taskID=28470951 <https://koji.fedoraproject.org/koji/taskinfo?taskID=28470951> https://bodhi.fedoraproject.org/updates/FEDORA-2018-3c876babb9 <https://bodhi.fedoraproject.org/updates/FEDORA-2018-3c876babb9> The new packages and versions are: * 389-ds-base-1.3.8.6-1 Source tarballs are available for download at Download 389-ds-base Source <https://releases.pagure.org/389-ds-base/389-ds-base-1.3.8.6.tar.bz2> Highlights in 1.3.8.6 * Bug fix 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.o… 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.3.8.6 * Ticket 49789 - backout original security fix as it caused a regression in FreeIPA

1 0

Announcing 389 Directory Server 1.4.0.13
by Mark Reynolds 20 Jul '18

20 Jul '18

389 Directory Server 1.4.0.13 The 389 Directory Server team is proud to announce 389-ds-base version 1.4.0.13 Fedora packages are available on Fedora 28 and 29(rawhide). Rawhide(F29) https://koji.fedoraproject.org/koji/taskinfo?taskID=28468953 <https://koji.fedoraproject.org/koji/taskinfo?taskID=28468953> F28 https://koji.fedoraproject.org/koji/taskinfo?taskID=28469862 <https://koji.fedoraproject.org/koji/taskinfo?taskID=28469862> https://bodhi.fedoraproject.org/updates/FEDORA-2018-f6a8f8036d <https://bodhi.fedoraproject.org/updates/FEDORA-2018-f6a8f8036d> The new packages and versions are: * 389-ds-base-1.4.0.13-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.13.tar.bz2> Highlights in 1.4.0.13 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 *dnf install 389-ds-base*, then run *dscreate*. For Cockput UI plugin use “dnf install cockpit-389-ds” See Install_Guide <http://www.port389.org/docs/389ds/howto/howto-install-389.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.o… 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.13 * Ticket 49854 - ns-slapd should create run_dir and lock_dir directories at startup * Ticket 49806 - Add SASL functionality to CLI/UI * Ticket 49789 - backout originali security fix from 1.4.0.12 as it caused a regression in FreeIPA * Ticket 49857 - RPM scriptlet for 389-ds-base-legacy-tools throws an error

1 0

Announcing 389 Directory Server 1.3.8.5
by Mark Reynolds 17 Jul '18

17 Jul '18

389 Directory Server 1.3.8.5 The 389 Directory Server team is proud to announce 389-ds-base version 1.3.8.5 Fedora packages are available on Fedora 27. https://koji.fedoraproject.org/koji/taskinfo?taskID=28375593 <https://koji.fedoraproject.org/koji/taskinfo?taskID=28375593> https://bodhi.fedoraproject.org/updates/FEDORA-2018-997817e633 <https://bodhi.fedoraproject.org/updates/FEDORA-2018-997817e633> The new packages and versions are: * 389-ds-base-1.3.8.5-1 Source tarballs are available for download at Download 389-ds-base Source <https://releases.pagure.org/389-ds-base/389-ds-base-1.3.8.5.tar.bz2> Highlights in 1.3.8.5 * Bug fixes and Security fix 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.o… 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.3.8.5 * Ticket 49789 - By default, do not manage unhashed password (Security Fix) * Ticket 49546 - Fix issues with MIB file * Ticket 49840 - ds-replcheck command returns traceback errors against ldif files having garbage content when run in offline mode * Ticket 48818 - For a replica bindDNGroup, should be fetched the first time it is used not when the replica is started * Ticket 49780 - acl_copyEval_context double free * Ticket 49830 - Import fails if backend name is “default” * Ticket 49432 - filter optimise crash * Ticket 49372 - filter optimisation improvements for common queries * Update Source0 URL in rpm/389-ds-base.spec.in

1 0

Announcing 389 Directory Server 1.4.0.12
by Mark Reynolds 17 Jul '18

17 Jul '18

389 Directory Server 1.4.0.12 The 389 Directory Server team is proud to announce 389-ds-base version 1.4.0.12 Fedora packages are available on Fedora 28 and 29(rawhide). Rawhide(F29) https://koji.fedoraproject.org/koji/taskinfo?taskID=28373966 <https://koji.fedoraproject.org/koji/taskinfo?taskID=28373966> F28 https://koji.fedoraproject.org/koji/taskinfo?taskID=28374438 <https://koji.fedoraproject.org/koji/taskinfo?taskID=28374438> https://bodhi.fedoraproject.org/updates/FEDORA-2018-f9e2994a41 <https://bodhi.fedoraproject.org/updates/FEDORA-2018-f9e2994a41> The new packages and versions are: * 389-ds-base-1.4.0.12-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.12.tar.bz2> Highlights in 1.4.0.12 Bug fixes and security fix Installation and Upgrade See Download <http://www.port389.org/docs/389ds/download.html> for information about setting up your yum repositories. To install, use *dnf install 389-ds-base*, then run *dscreate*. For Cockput UI plugin use “dnf install cockpit-389-ds” See Install_Guide <http://www.port389.org/docs/389ds/howto/howto-install-389.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.o… 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.12 * Ticket 48377 - Move jemalloc license to /usr/share/licences * Ticket 49813 - Revised interactive installer * Ticket 49789 - By default, do not manage unhashed password (Security Fix) * Ticket 49844 - lib389: don’t set up logging at module scope * Ticket 49546 - Fix issues with MIB file * Ticket 49840 - ds-replcheck command returns traceback errors against ldif files having garbage content when run in offline mode * Ticket 49640 - Cleanup plugin bootstrap logging * Ticket 49835 - lib389: fix logging * Ticket 48818 - For a replica bindDNGroup, should be fetched the first time it is used not when the replica is started * Ticket 49780 - acl_copyEval_context double free * Ticket 49830 - Import fails if backend name is “default” * Ticket 49832 - remove tcmalloc references * Ticket 49813 - dscreate - add interactive installer * Ticket 49808 - Add option to add backend to dscreate * Ticket 49811 - lib389 setup.py should install autogenerated man pages * Ticket 49795 - UI - add “action” backend funtionality * Ticket 49588 - Add py3 support for tickets : part-3 * Ticket 49820 - lib389 requires wrong python ldap library * Ticket 49791 - Update docker file for new dscreate options * Ticket 49761 - Fix more CI test issues * Ticket 49811 - Update man pages * Ticket 49783 - UI - add server configuration backend * Ticket 49717 - Add conftest.py for tests * Ticket 49588 - Add py3 support for tickets * Ticket 49793 - Updated descriptions in dscreate example INF file * Ticket 49471 - Rename dscreate options * Ticket 49751 - passwordMustChange attribute is not honored by a RO consumer if using “Chain on Update” * Ticket 49734 - Fix various issues with Disk Monitoring * Update Source0 URL in rpm/389-ds-base.spec.in

1 0

Failed modrdn operation
by Sergei Gerasenko 13 Jul '18

13 Jul '18

Hello, Somebody in my group was using an ipa command to rename a user’s login and the operation apparently failed. The audit log shows the operation was: dn: uid=userX,cn=users,cn=accounts,dc=ourdomain,dc=com changetype: modrdn newrdn: uid=userY deleteoldrdn: 1 … and the result was 1, which I assume is an error. Doing ldapsearch on "dn: uid=userY" returns nothing, but a search on “dn: uid=userX” returns: > ldapsearch -xLLL -h localhost -b cn=users,cn=accounts,dc=ourdomain,dc=com uid=userX dn: uid=userY,cn=users,cn=accounts,dc=ourdomain,dc=com uid: userY … So, searching for uid=userX returns uid=userY! Any ideas what could be going on? Dumping the database with db2ldif shows no mention of userY. So, I’m thinking that the transaction wasn’t committed and maybe restarting 389-ds will revert the bad change? Thanks! Sergei

1 1

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

389-users July 2018