389-users March 2020

389-users@lists.fedoraproject.org

13 participants
17 discussions

Replication with SSLCLIENTAUTH: server sent no certificate
by Eugen Lamers 01 Feb '21

01 Feb '21

I'm trying to setup a replication with a certificate based authentication between supplier and consumer. The certificates in the certdb at /etc/dirsrv/slapd-XXX contain the very same CA with which the respective server certificates in the certdbs have been signed. The certificates all have the 'u' flag, and the CA has the C and T flag. The replication (on the supplier) has been setup such that TLS and certificate based authentication is used, see extract from the replication agreement object: objectclass: nsds5ReplicationAgreement nsds5replicahost: <consumer-hostname> nsds5replicaport: 389 nsds5replicatransportinfo: TLS nsds5replicabindmethod: SSLCLIENTAUTH Trying to initialize the consumer raises this error in the error-log of the supplier (the host sending the starttls connection request): Replication bind with EXTERNAL auth failed: LDAP error 48 (Inappropriate authentication) (missing client certificate) The certificate that the server should have sent can, however, be used with the ldap commandline tools as ldapsearch. In this case a wireshark trace clearly shows that the client sends the certificate during the TLS handshake, while in the above case it doesn't. The TLS handshake defines that the client has to send an "empty certificate" if it does not have a certificate that has been issued by a CA offered by the server during the handshake. I can't see a reason for the client to think the condition isn't met. The certificate with which the server (supplier) is setup is the only one available. Is it possible that the server does not know which certificate it has to use for authentication with the consumer server? And if so, how do I make the server know? The 389-ds in use is the version 1.4.1.6~git0.5ac5a8aad. The problem was the same with 1.4.0.3. Thanks, Eugen

3 11

ERR - slapi_ldap_bind - Could not send bind request for id [(anon)] authentication mechanism [EXTERNAL]: error -1 (Can't contact LDAP server), system error 0 (no error), network error 0
by Graham Leggett 19 Nov '20

19 Nov '20

Hi all, We have a long standing 389ds master LDAP server that was found to be unable to contact it’s slaves. Most specifically, the slaves show nothing in their logs about any kind of connection, while the master is logging this: [12/Nov/2019:21:39:47.212715697 +0000] - ERR - slapi_ldap_bind - Could not send bind request for id [(anon)] authentication mechanism [EXTERNAL]: error -1 (Can't contact LDAP server), system error 0 (no error), network error 0 (Unknown error, host “ldap01:636”) Key is "system error 0 (no error)”, which leaves us stumped. The error is obviously “success”. Has anyone seen this kind of thing before? This is 389ds running on CentOS7 as follows: 389-ds-base-1.3.9.1-10.el7.x86_64 Regards, Graham —

3 8

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

replication problems
by Alberto Viana 12 May '20

12 May '20

Hey Guys, 389-Directory/1.4.2.8 389 (master) <=> 389 (master) In a master to master replication, start to see this error : [31/Mar/2020:17:30:52.610637150 +0000] - WARN - NSMMReplicationPlugin - replica_check_for_data_reload - Disorderly shutdown for replica dc=rnp,dc=local. Check if DB RUV needs to be updated Even after restart the service the problem persists, I have to disable and re-enable replication (and replication agr) on both sides, it works for some time, and the problem comes back. Any tips? Thanks Alberto Viana

4 24

Scripted letsencrypt certificate for 389-ds
by Laurent GUERBY 31 Mar '20

31 Mar '20

Hi, I installed 389-ds 1.4.0.21-1 on a debian 10 system. When I use cockpit in 389-ds tab I get "{'desc': 'Inappropriate authentication', 'info': 'SASL EXTERNAL bind requires an SSL connection'}" so I assume I must install a real certificate. Is there an official script I could use to configure and maintain a letsencrypt certificate on a fresh 389-ds install? The closest I could find (but not tried yet): https://git.dotlan.net/dhoffend/kolab/blob/73519a40f7adbfdb86394cfb2a0b 9eab39ac9757/debian-kolab16.1/update-letsencrypt.sh Thanks in advance, Sincerely, Laurent

3 9

Help in building Passsync
by LUCAS GUILHERME DIEDRICH 26 Mar '20

26 Mar '20

Hello guys, i'm trying to build passsync service, so i downloaded the code and i`m trying to build it on microsoft visual studio 2019. But when the build script try to download some file from port389.org it fails, can someone help me on building this? https://snipboard.io/ijCmR6.jpg -> Build Error log. Why am i doing this? So i'm migrating my old Freeipa Realm to a new one with AD pass replication, so all user are now in AD replicating the password to my new Freeipa Realm and Google, i would one more service to also replicate the password to my old Freeipa Realm, this to maintain compatibility while we migrating everything. So i download the project, rebrand it with 3892, changed the service name and register name, i think it will not interfere with the other process. Thanks a lot.

2 1

Announcing 389 Directory Server 1.4.1.16
by Mark Reynolds 16 Mar '20

16 Mar '20

389 Directory Server 1.4.1.16 The 389 Directory Server team is proud to announce 389-ds-base version 1.4.1.16 Fedora packages are available on Fedora 30. https://koji.fedoraproject.org/koji/taskinfo?taskID=42539571 <https://koji.fedoraproject.org/koji/taskinfo?taskID=42539571> - Fedora 30 Bodhi https://bodhi.fedoraproject.org/updates/FEDORA-2020-b9e37ebd1e <https://bodhi.fedoraproject.org/updates/FEDORA-2020-b9e37ebd1e> - Fedora 30 The new packages and versions are: * 389-ds-base-1.4.1.16-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.1.16.tar.bz2> Highlights in 1.4.1.16 * 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 the server use *dnf install 389-ds-base* To install the Cockpit UI plugin use *dnf install cockpit-389-ds* After rpm install completes, run *dscreate interactive* For upgrades, simply install the package. There are no further steps required. There are no upgrade steps besides installing the new rpms See Install_Guide <http://www.port389.org/docs/389ds/howto/howto-install-389.html> for more information about the initial installation and setup See Source <http://www.port389.org/docs/389ds/development/source.html> for information about source tarballs and SCM (git) access. New UI Progress (Cockpit plugin) The new UI is complete, and fully ported to React JS 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.1.16 * Issue 50499 - Fix npm audit issues * Issue 50884 - Health check tool DSEldif check fails * Issue 50926 - Remove dual spinner and other UI fixes * Issue 50928 - Unable to create a suffix with countryName * Issue 50758 - Only Recommend bash-completion, not Require * Issue 50904 - Connect All React Components And Refactor the Main Navigation Tab Code * Issue 50919 - Backend delete fails using dsconf * Issue 50872 - dsconf can’t create GSSAPI replication agreements * Issue 50914 - No error returned when adding an entry matching filters for a non existing automember group * Issue 50909 - nsDS5ReplicaId cant be set to the old value it had before * Issue 50898 - ldclt core dumped when run with -e genldif option -- 389 Directory Server Development Team

1 0

Announcing 389 Directory Server 1.4.2.9
by Mark Reynolds 16 Mar '20

16 Mar '20

389 Directory Server 1.4.2.9 The 389 Directory Server team is proud to announce 389-ds-base version 1.4.2.9 Fedora packages are available on Fedora 31. https://koji.fedoraproject.org/koji/taskinfo?taskID=42536258 <https://koji.fedoraproject.org/koji/taskinfo?taskID=42536258> - Fedora 31 Bodhi https://bodhi.fedoraproject.org/updates/FEDORA-2020-9d7e5f1469 <https://bodhi.fedoraproject.org/updates/FEDORA-2020-9d7e5f1469> The new packages and versions are: * 389-ds-base-1.4.2.9-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.2.9.tar.bz2> Highlights in 1.4.2.9 * 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 the server use *dnf install 389-ds-base* To install the Cockpit UI plugin use *dnf install cockpit-389-ds* After rpm install completes, run *dscreate interactive* For upgrades, simply install the package. There are no further steps required. There are no upgrade steps besides installing the new rpms See Install_Guide <http://www.port389.org/docs/389ds/howto/howto-install-389.html> for more information about the initial installation and setup See Source <http://www.port389.org/docs/389ds/development/source.html> for information about source tarballs and SCM (git) access. New UI Progress (Cockpit plugin) The UI is complete, and fully ported to React JS. 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.2.9 * Issue 50755 - setting nsslapd-db-home-directory is overriding db_directory * Issue 50937 - Update CLI for new backend split configuration * Issue 50499 - Fix npm audit issues * Issue 50884 - Health check tool DSEldif check fails * Issue 50926 - Remove dual spinner and other UI fixes * Issue 49845 - Remove pkgconfig check for libasan * Issue 50758 - Only Recommend bash-completion, not Require * Issue 50928 - Unable to create a suffix with countryName * Issue 50904 - Connect All React Components And Refactor the Main Navigation Tab Code * Issue 50919 - Backend delete fails using dsconf * Issue 50872 - dsconf can’t create GSSAPI replication agreements * Issue 50914 - No error returned when adding an entry matching filters for a non existing automember group * Issue 50909 - nsDS5ReplicaId cant be set to the old value it had before * Issue 50618 - support cgroupv2 * Issue 50898 - ldclt core dumped when run with -e genldif option -- 389 Directory Server Development Team

1 0

Announcing 389 Directory Server 1.4.3.4
by Mark Reynolds 16 Mar '20

16 Mar '20

389 Directory Server 1.4.3.4 The 389 Directory Server team is proud to announce 389-ds-base version 1.4.3.4 Fedora packages are available on Fedora 32 adn Rawhide. https://koji.fedoraproject.org/koji/taskinfo?taskID=42538967 <https://koji.fedoraproject.org/koji/taskinfo?taskID=42538967> - Rawhide (Fedora 33) https://koji.fedoraproject.org/koji/taskinfo?taskID=42538377 <https://koji.fedoraproject.org/koji/taskinfo?taskID=42538377> - Fedora 32 https://bodhi.fedoraproject.org/updates/FEDORA-2020-4520326fbb <https://bodhi.fedoraproject.org/updates/FEDORA-2020-4520326fbb> - Bodhi The new packages and versions are: * 389-ds-base-1.4.3.4-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.3.4.tar.bz2> Highlights in 1.4.3.4 * 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 the server use *dnf install 389-ds-base* To install the Cockpit UI plugin use *dnf install cockpit-389-ds* After rpm install completes, run *dscreate interactive* For upgrades, simply install the package. There are no further steps required. There are no upgrade steps besides installing the new rpms See Install_Guide <http://www.port389.org/docs/389ds/howto/howto-install-389.html> for more information about the initial installation and setup See Source <http://www.port389.org/docs/389ds/development/source.html> for information about source tarballs and SCM (git) access. New UI Progress (Cockpit plugin) The new UI is complete and fully ported to ReactJS 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.3.4 * Issue 50954 - Port buildnum.pl to python(part 2) * Issue 50955 - Fix memory leaks in chaining plugin * Issue 50954 - Port buildnum.pl to python * Issue 50947 - change 00core.ldif objectClasses for openldap migration * Issue 50755 - setting nsslapd-db-home-directory is overriding db_directory * Issue 50937 - Update CLI for new backend split configuration * Issue 50860 - Port Password Policy test cases from TET to python3 pwp.sh * Issue 50945 - givenname alias of gn from openldap * Issue 50935 - systemd override in lib389 for dscontainer * Issue 50499 - Fix npm audit issues * Issue 49761 - Fix CI test suite issues * Issue 50618 - clean compiler warning and log level * Issue 50889 - fix compiler issues * Issue 50884 - Health check tool DSEldif check fails * Issue 50926 - Remove dual spinner and other UI fixes * Issue 50928 - Unable to create a suffix with countryName * Issue 50758 - Only Recommend bash-completion, not Require * Issue 50923 - Fix a test regression * Issue 50904 - Connect All React Components And Refactor the Main Navigation Tab Code * Issue 50920 - cl-dump exit code is 0 even if command fails with invalid arguments * Issue 50923 - Add test - dsctl fails to remove instances with dashes in the name * Issue 50919 - Backend delete fails using dsconf * Issue 50872 - dsconf can’t create GSSAPI replication agreements * Issue 50912 - RFE - add password policy attribute pwdReset * Issue 50914 - No error returned when adding an entry matching filters for a non existing automember group * Issue 50889 - Extract pem files into a private namespace * Issue 50909 - nsDS5ReplicaId cant be set to the old value it had before * Issue 50686 - Port fractional replication test cases from TET to python3 final * Issue 49845 - Remove pkgconfig check for libasan * Issue:50860 - Port Password Policy test cases from TET to python3 bug624080 * Issue:50860 - Port Password Policy test cases from TET to python3 series of bugs * Issue 50786 - connection table freelist * Issue 50618 - support cgroupv2 * Issue 50900 - Fix cargo offline build * Issue 50898 - ldclt core dumped when run with -e genldif option -- 389 Directory Server Development Team

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

389-users March 2020