389-users October 2019

389-users@lists.fedoraproject.org

22 participants
25 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

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

Re: urp_fixup_add_cenotaph errors
by Morgan, Iain (ARC-TN)[InuTeq, LLC] 04 Nov '19

04 Nov '19

On 9/8/19, 15:40, "William Brown" <wbrown(a)suse.de> wrote: > On 7 Sep 2019, at 08:33, Morgan, Iain (ARC-TN)[InuTeq, LLC] <iain.morgan(a)nasa.gov> wrote: > > Hello Marc, > > Yes, it is 389-ds-base1.3.9.1-10.el7, but we are not using IPA and there are no memberOf plugin errors. The actual modrdn operations have error=0. If we may, can we ask what the modrdn operations were, and to ask a little about your tree layout so we could try to understand more about this? Sure, there's nothing unusual regarding the tree layout. There's a single backend with ou=People,.... and ou=Groups,.... One thing that may be relevant is that this is a stand-alone server -- replication has not been configured. From the access log: [09/Sep/2019:15:05:08.577399600 -0700] conn=2233897 op=2 SRCH base="ou=Groups,dc=nas,dc=nasa,dc=gov" scope=2 filter="(|(cn=temp)(cn=testgroup))" attrs="cn" [09/Sep/2019:15:05:08.577630700 -0700] conn=2233897 op=2 RESULT err=0 tag=101 nentries=1 etime=0.0000323261 [09/Sep/2019:15:05:08.578316196 -0700] conn=2233897 op=3 MODRDN dn="cn=temp,ou=Groups,dc=nas,dc=nasa,dc=gov" newrdn="cn=testgroup" newsuperior="(null)" [09/Sep/2019:15:05:08.581595207 -0700] conn=2233897 op=3 RESULT err=0 tag=109 nentries=0 etime=0.0003326527 From the errors log: [09/Sep/2019:15:05:08.580235717 -0700] - ERR - conn=2233897 op=3 - urp_fixup_add_cenotaph - failed to add cenotaph, err= 21 -- Iain Morgan

3 6

When 389ds will be available on CentOS 8
by wodel youchi 31 Oct '19

31 Oct '19

Hi, Is there any news about the availability of 389DS on CentOS8? Regards.

6 8

Building 389 rpm on CentOS 8 from source rpm
by Ivanov Andrey (M.) 31 Oct '19

31 Oct '19

Hi, m trying to build the 389 on CentOS 8 from rpm source package. When i do yum-builddep SPECS/389-ds-base.spec i have a missong component - "No matching package to install: 'python3-argparse-manpage'". I could not find a corresponding package in any of the repositories of CentOS 8 (AppStream/BaseOS/PowerTools/epel/extras). If i try to disable this requirement in spec by cpommenting the following line: BuildRequires: python%{python3_pkgversion}-argparse-manpage the "rpmbuild -ba SPECS/389-ds-base.spec" stops at the same package requirement when it starts to build lib389: + pushd ./src/lib389 ~/rpmbuild/BUILD/389-ds-base-1.4.0.20-10/src/lib389 ~/rpmbuild/BUILD/389-ds-base-1.4.0.20-10 + CFLAGS='-O2 -g -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -fexceptions -fstack-protector-strong -grecord-gcc-switches -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection' + LDFLAGS='-Wl,-z,relro -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld' + /usr/libexec/platform-python setup.py build '--executable=/usr/libexec/platform-python -s' Traceback (most recent call last): File "setup.py", line 17, in <module> from build_manpages import build_manpages ModuleNotFoundError: No module named 'build_manpages' error: Bad exit status from /var/tmp/rpm-tmp.OOJPV1 (%build) RPM build errors: Macro expanded in comment on line 117: %{python3_pkgversion}-argparse-manpage Bad exit status from /var/tmp/rpm-tmp.OOJPV1 (%build) Where do i obtain the corresponding package ( python3-argparse-manpage ) for CentOS8? I have not tried to build on RHEL8, maybe that package exists in RHEL8 vut not CentOS 8? Thank you! Regards, Andrey

2 2

How to disable listening to plain (non-TLS) connections?
by Erhan S 29 Oct '19

29 Oct '19

Hello everyone, I am running 389ds at the moment and want to know how I can disable 389ds listening to plain (non-TLS) connections, so that the 389 port is basically disabled and only TLS connections are possible. Thanks for your help!

2 2

Change User DS in Admin Server with command line
by Nicolas Martin 29 Oct '19

29 Oct '19

Hello everyone, Since disabling the non secure port 389, I need to change the "User DS" setting of the admin server. I can do it fine with the GUI in the tab "User DS" and set my User Directory settings. However, I can't find which configuration file or ldap entry I need to modify to set it through command line; I need to script it. Could you advise me how to change it ? Regards, Nicolas Martin

3 4

master to master replication cfg Q
by Ghiurea, Isabella 24 Oct '19

24 Oct '19

Hi List, I have a question regarding the cfg for a slave replication ldap server: we have 2 DS cfg as master to master replication with only one acting as write DS at a given time, now we have a business request to cfg the third ldap server but as slave ( only read). I need to know if would be sufficient to cfg only one replication agreement from one of the master DS to this new slave DS host will this be sufficient or need one agreement for each one of the maste to slave ( 2 separate rep agreements) ? thank you Isabella

5 6

Binding when using database links
by Vandenburgh, Steve Y 17 Oct '19

17 Oct '19

With database links - when connecting from one server to the linked-server, it is possible to rebind as the user instead of using specific proxy credentials? Thanks, Steve Vandenburgh This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.

2 1

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

389-users October 2019