389-users May 2015

389-users@lists.fedoraproject.org

17 participants
16 discussions

flag "user must change password at next logon" remains active after PassSync
by Mihai Carabas 20 May '15

20 May '15

Hello, We've setup an 389 Directory Server on a Fedora21 and configured synchronization with an Active Directory (running on an Windows2012R2 Datacenter). We've managed to synchronize all the accounts from the 389DS to AD (about 44000). All the accounts have the "user must change password at next logon" in the AD, even if the users change their passwords on the 389DS, The password gets to the AD, but the flag for "user must change password at next logon" still remains active (basically forces the user to change their password on the Active Directory). Is there any workaround for this? The attribute passwordMustChange in the 389DS is set to Off. Thank you, Mihai Carabas University POLITEHNICA of Bucharest

2 2

Limit on number of databases per directory server instance
by Colin Tulloch 19 May '15

19 May '15

Hi all - Is there a limit to the number of databases that can be present on an instance of directory server - or on a server/VM itself? Some colleagues of mine seem to believe there is a limit of 10 DBs per server. I haven't seen this in the Redhat documentation myself (we run RHDS, not necessarily 389). Colin Tulloch Cloud Services Architect

3 5

DS querying members groups not showing recent/updated members
by Ghiurea, Isabella 15 May '15

15 May '15

HI LIst, we are seeing some strange behavoiurs in our DS ( members of pluging is enabled) if we add a user to a group we can't see that new user in group for some minutes /days , the follwing curl returns 0 members in group but ( there were already 2 members+ 1 added ) running same curl command today (2 days later) the group memberships now show up as expected: curl -v -u xxxxxx "http://www.ababababababb? ID=xxxx&IDTYPE=http&ROLE=member" So, there is something in LDAP which is taking a long time and is affecting group queries. we wol;d like to know if this can be a case when using 'membership plugin' that aggregates user membership for reporting? ' Thank you

3 2

Migrating from openldap/slapd to 389
by Bobby Krupczak 14 May '15

14 May '15

Hi! Hey, I'm sure you guys are tired of folks asking this question but I've spent the last day searching the InterWebs and still have questions. I'm fixing to switch from openldap/slapd to 389 for ldap authentication for linux and samba clients. I want to run the 389 dir service on the same system as slapd. - Is the switch as simple as turning on the 389 server, turning off slapd, and importing my user account objects into 389 via a ldif? - If I'm only using slapd for "standard" login accounts and passwords, do I still need to import any schemas from slapd? (It looks like 389 has the same basic schemas) - I've used slapcat and ldapsearch to create ldif files of my user objects. Do I need to munge these ldif entries in order to import them into 389? - I didnt see specific instructions for enabling and turning on the web admin interface for 389. Is it turned on automatically when I start 389 server? - Is the switch transparent to linux/unix ldap clients or will I need to go re-configure them? Thanks, Bobby

2 1

a problem with the EPEL repository and dependencies
by Giovanni Baruzzi 08 May '15

08 May '15

Dear 389 friends, I have a problem with a simple installation of port389 under CentOS using the EPEL repository. After configuring EPEL as described under http://www.port389.org/docs/389ds/download.html, I can begin with the installation of the modules using yum. The installation of 389-ds-base-libs.x86_64 and 389-ds-base.x86_64 was without any problem but the installation of 389-adminutil.x86_64 stopped with the following message: === Resolving Dependencies --> Running transaction check ---> Package 389-adminutil.x86_64 0:1.1.21-2.el7 will be installed --> Processing Dependency: libicuuc.so.50()(64bit) for package: 389-adminutil-1.1.21-2.el7.x86_64 --> Processing Dependency: libicui18n.so.50()(64bit) for package: 389-adminutil-1.1.21-2.el7.x86_64 --> Processing Dependency: libicudata.so.50()(64bit) for package: 389-adminutil-1.1.21-2.el7.x86_64 --> Finished Dependency Resolution Error: Package: 389-adminutil-1.1.21-2.el7.x86_64 (epel) Requires: libicudata.so.50()(64bit) Error: Package: 389-adminutil-1.1.21-2.el7.x86_64 (epel) Requires: libicuuc.so.50()(64bit) Error: Package: 389-adminutil-1.1.21-2.el7.x86_64 (epel) Requires: libicui18n.so.50()(64bit) You could try using --skip-broken to work around the problem You could try running: rpm -Va --nofiles —nodigest === Interestingly enough the server (a cloud server) with a very basic CentOS installation, has already the libicu installed already at the last version: Libicu.x86_64 4.2.1_9.1.el6_2 Libicu.i686 4.2.1_9.1.el6_2 Libicu-devel.x86_64 4.2.1_9.1.el6_2 Any Idea about how can I recover from the problem? Thank you, Giovanni

1 0

389-ds and mapping an authenticated windows client drive to NFS shares
by Mike 05 May '15

05 May '15

Hello 389-ds, I have experience with the Samba 3 series providing NT style primary domain controllers and have recently been testing Samba 4 Active Directory capabilities. I'm not so sure my network is improved by adding more Microsoft Active Directory standards in managing computers, users, and network resources. I am interested in testing 389 directory server for its easily replicated Multi-Master feature, LDS, and secure authentication. I will use pGina to connect Windows clients to the 389 DS resources and need to know if it's possible to "map" NFS shares on the server so they are browseable by the windows clients. Does anyone use a setup like this with their 389 directory server? Thank you for your help. Best regards, Mike

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

389-users May 2015