389-users October 2018

389-users@lists.fedoraproject.org

11 participants
20 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

Announcing 389 Directory Server 1.3.9.0
by Mark Reynolds 31 Oct '18

31 Oct '18

389 Directory Server 1.3.9.0 The 389 Directory Server team is proud to announce 389-ds-base version 1.3.9.0 Fedora packages are available on Fedora 27. https://koji.fedoraproject.org/koji/taskinfo?taskID=30581994 <https://koji.fedoraproject.org/koji/taskinfo?taskID=30581994> Bodhi https://bodhi.fedoraproject.org/updates/FEDORA-2018-8adbba96b5 <https://bodhi.fedoraproject.org/updates/FEDORA-2018-8adbba96b5> The new packages and versions are: * 389-ds-base-1.3.9.0-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.9.0.tar.bz2> Highlights in 1.3.9.0 * Bug and security fixes Installation and Upgrade See Download <https://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 <https://www.port389.org/docs/389ds/legacy/install-guide.html> for more information about the initial installation, setup, and upgrade See Source <https://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 * Branching 1.3.8 to 1.3.9 * Ticket 49967 - entry cache corruption after failed MODRDN * Ticket 49968 - Confusing CRITICAL message: list_candidates - NULL idl was recieved from filter_candidates_ext * Ticket 49915 - fix compiler warnings (2nd) * Ticket 49915 - fix compiler warnings * Ticket 49915 - Master ns-slapd had 100% CPU usage after starting replication and replication cannot finish

1 0

issues with password encryption changes after upgrade
by Ghiurea, Isabella 31 Oct '18

31 Oct '18

Hi list, we upgrade from1.3.5.15-1.fc24, to 1.3.7.5-24.el7 , this a multi master replication environment we are seeing the paswd encryption for new users in new 389-DS has been changed and is causing some grief , both version have the start of passwd same string :'e1NTSE" , BUT the latest 389-DS e has one additional new line . Is there anything we can do to have same encryption pattern ? Thank you

2 3

Adding additional optional attritubes
by Tina Fora 31 Oct '18

31 Oct '18

Hi All, I'm running 389-ds-1.2.2-1.el6. I would like to add two optional attributes for something like Supervisor/Advisor Name and Email. This is what I have now. Looking for some info on how to go about testing and making this change. # ldapsearch -xLLL uid=ldapfoo dn: uid=ldapfoo,ou=People,dc=burr,dc=example,dc=edu memberOf: cn=boss,ou=groups,dc=burr,dc=example,dc=edu memberOf: cn=tgi,ou=groups,dc=burr,dc=example,dc=edu uid: ldapuser objectClass: top objectClass: person objectClass: organizationalPerson objectClass: inetorgperson objectClass: inetuser objectClass: posixAccount objectClass: ldapPublicKey objectClass: examplePerson objectClass: systemQuotas exampleEduPersonNetID: ldapfoo cn: Foo Bar gidNumber: 767 homeDirectory: /home/ldapuser sn: Fora givenName: Foo loginShell: /bin/bash mail: ldapuser(a)example.edu quota: /home:10485760,10485760,0,0 uidNumber: 10170

2 1

Re: Track constraint violation due password policy
by Mark Reynolds 31 Oct '18

31 Oct '18

On 10/31/18 10:37 AM, Alberto Viana wrote: > Hi Mark, > > In access log the behavior is exactly how you said (small description): > "invalid password syntax" Yeah a bit vague :-( I opened this RFE ticket: https://pagure.io/389-ds-base/issue/50002 --> Feel free to add any comments, requests, or suggestions I'm not sure what version this will land in, but what version of 389-ds-base are you using? Thanks, Mark > > I know that's related to password policy, but it's really bad not > known which item exactly. In some cases the users could provide me the > password and I can analyse, but in some cases not, so I think that > should exist something in 389 to show to us(admin) that. > > Thanks anyway for your help. > > > On Wed, Oct 31, 2018 at 11:27 AM Mark Reynolds <mreynolds(a)redhat.com > <mailto:mreynolds@redhat.com>> wrote: > > Hi Alberto, > > Did you check the access log? There "should" be a small text > message that said what syntax was violated on the RESULT line in > the access log. Just grep for err=19 in the access logs. Let me > know if you find it. But that's all there would be for > troubleshooting this. Checking the current passwd policy code we > don't have any useful logging in there - we only send small > descriptions of the error back to the client. > > So this inspires me to add a new error log level for tracking > password policy behavior. I will open a new ticket for that RFE > shortly... > > Thanks, > > Mark > > On 10/31/18 10:12 AM, Alberto Viana wrote: >> Hi Guys, >> >> There's any way to log or track constraint violation reason? >> >> Once We have 2 environments I need to track when an user could >> change password on windows side but this password could not be >> replicated to 389 due to password policy . >> >> I can see this on passsync log: >> >> 10/30/18 18:43:38: Searching for (ntuserdomainid=my.user) >> 10/30/18 18:43:38: Ldap error in ModifyPassword >> 19: Constraint violation >> 10/30/18 18:43:38: Modify password failed for remote entry: >> uid=my.user,ou=users,dc=my,dc=domain >> >> But I need to know which item on password policy has been violated >> >> >> Thanks >> >> _______________________________________________ >> 389-users mailing list --389-users(a)lists.fedoraproject.org <mailto:389-users@lists.fedoraproject.org> >> To unsubscribe send an email to389-users-leave(a)lists.fedoraproject.org <mailto:389-users-leave@lists.fedoraproject.org> >> Fedora Code of Conduct:https://getfedora.org/code-of-conduct.html >> List Guidelines:https://fedoraproject.org/wiki/Mailing_list_guidelines >> List Archives:https://lists.fedoraproject.org/archives/list/389-users@lists.fedo… >

1 0

Track constraint violation due password policy
by Alberto Viana 31 Oct '18

31 Oct '18

Hi Guys, There's any way to log or track constraint violation reason? Once We have 2 environments I need to track when an user could change password on windows side but this password could not be replicated to 389 due to password policy . I can see this on passsync log: 10/30/18 18:43:38: Searching for (ntuserdomainid=my.user) 10/30/18 18:43:38: Ldap error in ModifyPassword 19: Constraint violation 10/30/18 18:43:38: Modify password failed for remote entry: uid=my.user,ou=users,dc=my,dc=domain But I need to know which item on password policy has been violated Thanks

2 1

Announcing 389-console 1.1.19
by Mark Reynolds 18 Oct '18

18 Oct '18

389 Console 1.1.19 The 389 Directory Server team is proud to announce 389-console version 1.1.19 Fedora packages are available from the Fedora 28, Fedora 29 and Rawhide repositories. Fedora 29 https://koji.fedoraproject.org/koji/taskinfo?taskID=30316371 <https://koji.fedoraproject.org/koji/taskinfo?taskID=30316371> Fedora 28 https://koji.fedoraproject.org/koji/taskinfo?taskID=30316405 <https://koji.fedoraproject.org/koji/taskinfo?taskID=30316405> The new packages and versions are: * 389-console-1.1.19-1 Source tarballs are available for download at Download 389-ds-base Source <https://releases.pagure.org/389-console/389-console-1.1.19.tar.bz2> Installation and Upgrade See Download <https://www.port389.org/docs/389ds/download.html> for information about setting up your yum repositories. To install, use *dnf install 389-console* To upgrade, use *dnf upgrade 389-console* See Install_Guide <https://www.port389.org/docs/389ds/legacy/install-guide.html> for more information about the initial installation, setup, and upgrade See Source <https://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… and following pages: If you find a bug, or would like to see a new feature, file it in our Trac instance: https://pagure.io/389-console/new_issue Detailed Changelog since 389-console-1.1.18 * Add JSS’s dependencies to the classpath of 389-console

1 0

Password policy not working
by Nick W. Harrison 16 Oct '18

16 Oct '18

Hello - I have a password policy on the OU that contains all of my user accounts. This password policy is set on the subtree and the "user may change password" option is deselected. However, I'm still able to change my password if I use passwd on a LDAP client. I'm running an older version of 389-ds...v.1.2.2-6...and am wondering if there is anything additional I need to put in place to prevent users from changing their passwords. My accounts and passwords are replicated over from AD with a unidirectional relationship, and the clients are doing simple binds. Thanks for any thoughts.

2 4

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

389-users October 2018