openldap-technical

openldap-technical@openldap.org

9 participants
9902 discussions

Automatically create home directory uppon Email login
by Stelios A. 22 Jul '08

22 Jul '08

Hello all, I've migrate an old Sun Directory Server to OpenLDAP (version 2.4.9 on Ubuntu 8.04 server) and setup a master/slave with syncrepl for data replication betwwen 2 servers. 1st server hold the master ldap and second the slave along with the email server (Sendmail + Dovecot). Email server requires ofcourse a home directory with a mbox file etc. Is there a way to avoid creating each users home directory and setup then his/her permissions? There are 980 users in the base dc and trying to figure out a way to avoid creating all this directories along with chmod manually. I've already setup pam to auto create home directory uppon user login but problem is that only 5 users will have access via ssh. Any ideas? Thanks a lot

3 4

Client connect issues with OpenLDAP 2.3 on RHEL 4
by Martin Benson 21 Jul '08

21 Jul '08

I have a Red Hat Enterprise Linux v4.4 installation that runs OpenLDAP 2.2 using the provided Red Hat rpm's. I want to upgrade this to OpenLDAP 2.3 and have created an LDAP server using the packages from http://staff.telkomsa.net/packages/rhel4/openldap/i386 . The problem I have is that I cannot get a client to attach or query the server. I have installed the openldap2.3-clients and openldap2.3 packages and the server with logging enabled does not even show a connection. I suspect it is a problem with the nss_ldap package that comes bundled with RHEL 4.4. I cannot compile the software on my system as it is a partial install for clients of ours and does not get delivered with compiler software. Does anyone know of an updated rpm for nss_ldap to be compatible with openldap2.3 and RHEL 4? Has anyone done the install and written an install guide? Thanks Martin

2 1

Reg:Design of openldap
by Chakri 21 Jul '08

21 Jul '08

Hi, i'm a newbie to this ldap world.But i have been spending so much time to understand the design of openldap-2.3.39. I wanted to understand the process flow during the functioning of slapd. can some one tell me where can i get the design documents of openldap....plz help...

1 0

memberOf search ACLs
by Andrew Bartlett 21 Jul '08

21 Jul '08

I've recently been trying to lock down Samba4's default ACLs, in it's generated LDAP backend configuration. I have memberOf configured to 'error' on dangling links, which I need for Samba. But I seem to be having some trouble with ACLs. I've attached my full config file, but the key part is: access to dn.base="" by dn=cn=samba-admin,cn=samba manage by anonymous read by * read access to dn.subtree="cn=samba" by anonymous auth access to dn.subtree="${DOMAINDN}" by dn=cn=samba-admin,cn=samba manage by * none If I change the last line to 'by * read', then the error is returned, but otherwise (due apparently to "" being unable to read the entry to validate it's existence). Shouldn't the search operations happen as the rootdn or memberof-dn, or am I missing some other configuration element here? In trying to fix this, I looked at what seemed to by typos in memberof.c, the patch of which I attach, but this didn't help. Any thoughts? Thanks, Andrew Bartlett -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org Samba Developer, Red Hat Inc.

2 5

Re: BDB selection, et al.
by William Jojo 20 Jul '08

20 Jul '08

---- Original message ---- >Date: Sat, 19 Jul 2008 04:33:46 -0700 >From: Howard Chu <hyc(a)symas.com> >Subject: Re: BDB selection, et al. >To: Quanah Gibson-Mount <quanah(a)zimbra.com> >Cc: William Jojo <jojowil(a)hvcc.edu>,openldap-technical(a)openldap.org > >Quanah Gibson-Mount wrote: >> --On Friday, July 18, 2008 9:11 PM -0400 William Jojo<jojowil(a)hvcc.edu> >> wrote: > >>> I have noticed that the Symas packages user BDB 4.2 (with 2.3.42) as does >>> Ubuntu with 2.4.9+. I was wondering what the preference is over 4.4 >>> (which I use) and 4.[67]. >> >> 4.2.52 + patches has the longest history of being solid. >> >> 4.3 was a disaster >> >> 4.4 was likely okay >> >> 4.5 was likely okay >> >> 4.6 also seems okay, and has some useful improvements >> >> 4.7 is not yet supported, but will be in a future release, and has >> additional useful improvements over 4.6. > >4.7 can be made to work, if you're willing to tweak things a bit. The memory >manager in 4.6 is much improved over earlier versions; the memory manager in >4.7 is slightly better still. The lock manager in 4.7 is more efficient in >multi-core systems than in previous versions. > Do you, Howard, consider BDB 4.4 stable? I originally worked on 4.2 for initial rollout some years ago. Admittedly, I have no problems at present with 4.4, and I could be convinced to step backward if there is a compelling reason to do so. >>> I ask because I build OpenLDAP (among other things) for AIX 5.2/5.3/6.1 >>> at (shameless plug) http://pware.hvcc.edu/ and I was considering moving >>> to 2.4.10 with BDB 4.6, but now I am not certain where to go for a few of >>> reasons: >>> >>> * Why the choice to stay with BDB 4.2? >> >> Proven track record over later releases (4.4, 4.5) for stability and >> performance. >> >>> * And OpenSSL 0.9.7l (over the 0.9.8 series)? >> >> I use OpenSSL 0.9.8 in my builds and have for ages. > >The Symas OpenLDAP 2.4 packages also use OpenSSL 0.9.8. However, the OpenSSL >build system changed, making it more difficult to complete the Windows build. >That's one of the reasons we stayed with 0.9.7 for so long in our OpenLDAP 2.3 >packages. >> >>> * 2.3.39 has been *stable* since 11/2007 and I have not moved from that >>> point within the software suite offered. Is a later version of 2.3 going >>> to be marked stable (like 2.3.42.1 is in the Symas prodcut). >> >> Not likely. > >True, no further 2.3.x release will be marked Stable. > >> Stable is really a fairly meaningless term. > >False. At the time that a release was marked stable, it was considered the >most stable release. I.e., after sufficient amount of time in release, no >major issues were discovered. > >> Assigning meaning >> to it as a guideline as to what version to build is a very bad idea. >> There's a major DoS vulnerability in 2.3.39, for example, that was fixed in >> 2.3.43 and 2.4.11. > >It's important to note that the Stable marker only changes if there's a new >release that we consider stable. The subsequent discovery of bugs in a Stable >release won't trigger the removal of that marker. So 2.3.39 is still marked >Stable, even though important bug fixes are in 2.3.43, because those bugs were >discovered long after 2.3.39 was released. > So, I guess I will stay where I am in production and prepare for a 2.4 upgrade at some soon time after I finish my testing in 2.4 and when a stable release is announced. >In the meantime, when moving the Stable marker, the Project's practice has >been that it can only be moved to the Current release stream, which is 2.4. >But we haven't yet seen a 2.4 release remain long enough in public use without >new issues quickly being discovered. So there is not yet a new Stable release. > >>> * 2.4.x seems stable enough to me and certainly to Ubuntu x86[_64], but I >>> would like some other indication that I should make the leap before I >>> begin to change dependencies to several of the products I produce. Is >>> 2.4.x going to be marked stable in the near future? > >> Hopefully. Note that stable does not remotely mean bug free (or relatively >> low in bug count). It simply means stable as far as core (i.e., not new) >> functionality is concerned. > >No. It means low bug count as of a particular point in time, e.g., within a >couple weeks after the release. > >And as I recall, we need to get to a feature freeze in the core code first. I >think 2.4 is just about at this point now. > Superb. Thank you very much, Quanah and Howard. It has been a very enlightening discussion. Cheers, Bill >-- > -- Howard Chu > CTO, Symas Corp. http://www.symas.com > Director, Highland Sun http://highlandsun.com/hyc/ > Chief Architect, OpenLDAP http://www.openldap.org/project/ >

1 0

Please help me with ppolicy pwdReset
by Scott Classen 19 Jul '08

19 Jul '08

Hi All, this is my default ppolicy: dn: cn=default,ou=Policies,dc=example,dc=com objectClass: pwdPolicy objectClass: top objectClass: device pwdAttribute: userPassword pwdMaxFailure: 3 pwdFailureCountInterval: 0 pwdAllowUserChange: TRUE cn: default pwdSafeModify: FALSE pwdExpireWarning: 0 pwdInHistory: 1 pwdMinLength: 7 pwdGraceAuthNLimit: 1 pwdLockout: TRUE pwdLockoutDuration: 300 pwdMaxAge: 63072000 pwdCheckQuality: 2 pwdMustChange: TRUE pwdMinAge: 0 Here is an example of a user with their pwdReset attribute set to TRUE. I've only included the relevant lines: dn: uid=newguy,ou=People,dc=example,dc=com pwdChangedTime: 20080718234642Z pwdReset: TRUE pwdPolicySubentry: cn=default,ou=Policies,dc=example,dc=com Shouldn't this user be requested to change their password the next time the log in? Well they're not. logins a successful and there is no prompting for a new password. Can someone please help me trouble shoot this? Thanks, Scott

1 1

RES: ppolicy woes
by Gustavo Mendes de Carvalho 19 Jul '08

19 Jul '08

Hi Bob, Some months ago I had similar problem trying to use Password Policy. I was using RHAS4 Up6, and my client machines was using RHES4 Up2, and for some unknown reason, no matter waht configuration I did, client machines did not recognizes ppolicy arguments sent from ldap server. I just solved this situation doing some upgrade in client machines, from Up2 to Up5. After this upgrade, everithing was OK. Did you try this client configuration in some other linux distribution ? --- Gustavo Mendes de Carvalho email: gmcarvalho(a)gmail.com

1 0

BDB selection, et al.
by William Jojo 19 Jul '08

19 Jul '08

I have noticed that the Symas packages user BDB 4.2 (with 2.3.42) as does Ubuntu with 2.4.9+. I was wondering what the preference is over 4.4 (which I use) and 4.[67]. I ask because I build OpenLDAP (among other things) for AIX 5.2/5.3/6.1 at (shameless plug) http://pware.hvcc.edu/ and I was considering moving to 2.4.10 with BDB 4.6, but now I am not certain where to go for a few of reasons: * Why the choice to stay with BDB 4.2? * And OpenSSL 0.9.7l (over the 0.9.8 series)? * 2.3.39 has been *stable* since 11/2007 and I have not moved from that point within the software suite offered. Is a later version of 2.3 going to be marked stable (like 2.3.42.1 is in the Symas prodcut). * 2.4.x seems stable enough to me and certainly to Ubuntu x86[_64], but I would like some other indication that I should make the leap before I begin to change dependencies to several of the products I produce. Is 2.4.x going to be marked stable in the near future? I appreciate all of the work of the OpenLDAP team and the community. I welcome any suggestions to help me make the right decision. In the meantime, my own production servers remain at 2.3.39-stable, but I can be persuaded to upgrade. :-) Cheers, Bill

3 2

ppolicy woes
by Robert Evans 18 Jul '08

18 Jul '08

Greetings, I've been trying to get openldap working with the ppolicy stuff for the last week. I think I've got things setup correctly, but the account lockout stuff isn't working and I can't figure out what I've done wrong. I've attached below the slapd.conf, ldap.conf and the ldif file I used to set up the test server. I'm relatively inexperienced in LDAP so I double checked things, but maybe.... If I include the ACL access part in the slapd.conf file (shown below), I can't ssh into a client that is using the server to authenticate. If I remove the access section, I can connect just fine, but then it authenticates me even though an ldapsearch with the -e ppolicy flag shows "ldap_bind: Invalid credentials (49); Account locked" I'm running openldap 2.3.39 on Cent OS 5.0. I'm starting ldap with the -d -1 option and don't see any error messages. Any suggestions? Thanks, Bob ================================ Below are the files used to populate the ppolicy attributes, and the slapd.conf and ldap.conf files on the server. =============================== 1) The following was used to populate the LDAP server, with the top level objects and the ppolicy values =============================== dn: dc=foo,dc=bar,dc=edu objectClass: top objectClass: organization objectClass: dcObject o: foo dc: foo dn: ou=People, dc=foo,dc=bar,dc=edu objectClass: top objectClass: organizationalUnit ou: People dn: ou=Group,dc=foo,dc=bar,dc=edu objectClass: top objectclass: organizationalUnit ou: Group dn: ou=Policies, dc=foo,dc=bar,dc=edu objectClass: top objectClass: organizationalUnit ou: Policies dn: cn=Standard Policy, ou=Policies, dc=foo,dc=bar,dc=edu objectClass: top objectClass: device objectClass: pwdPolicy cn: Standard Policy pwdAttribute: 2.5.4.35 # min passwd change of 7 days pwdMinAge: 604800 # max passwd change of 90 days pwdMaxAge: 7776000 # expire warning in 7 days pwdExpireWarning: 604800 # Can't reuse the last 24 passwords pwdInHistory: 24 # the server must verify the new passwd for changes to be made pwdCheckQuality: 2 # min passwd length pwdMinLength: 8 # Number of failed passwd attempts before lockout pwdMaxFailure: 3 # lockout user for failed attempts pwdLockout: TRUE # only lockout user for 15 minutes pwdLockoutDuration: 900 # Do not allow expired passwd's to access system pwdGraceAuthNLimit: 0 # only reset passwd attempt count on successful login pwdFailureCountInterval: 0 # specifies user must change passwd after admin has reset it pwdMustChange: TRUE # users can change their passwords pwdAllowUserChange: TRUE # Allows the user to change their passwd without typing in the old. pwdSafeModify: TRUE =============================== 2) Here is the slapd.conf file =============================== # master slapd config -- for testing # $OpenLDAP: pkg/ldap/tests/data/slapd-ppolicy.conf,v 1.6.2.7 2007/01/02 21:44:12 kurt Exp $ ## This work is part of OpenLDAP Software <http://www.openldap.org/>. ## ## Copyright 1998-2007 The OpenLDAP Foundation. ## All rights reserved. ## ## Redistribution and use in source and binary forms, with or without ## modification, are permitted only as authorized by the OpenLDAP ## Public License. ## ## A copy of this license is available in the file LICENSE in the ## top-level directory of the distribution or, alternatively, at ## <http://www.OpenLDAP.org/license.html>. include /etc/openldap/schema/core.schema include /etc/openldap/schema/cosine.schema include /etc/openldap/schema/inetorgperson.schema include /etc/openldap/schema/openldap.schema include /etc/openldap/schema/nis.schema include /etc/openldap/schema/ppolicy.schema pidfile /var/lib/ldap/run/slapd.pid argsfile /var/lib/ldap/run/slapd.args #mod#modulepath ../servers/slapd/back-bdb/ #mod#moduleload back_bdb.la #monitormod#modulepath ../servers/slapd/back-monitor/ #monitormod#moduleload back_monitor.la modulepath /usr/sbin/openldap/ moduleload ppolicy.la ####################################################################### # database definitions ####################################################################### database bdb suffix "dc=foo,dc=bar,dc=edu" directory /var/lib/ldap/openldap-data rootdn "cn=Manager,dc=foo,dc=bar,dc=edu" rootpw {SSHA}<root slappasswd went here> index objectClass eq #hdb#index objectClass eq #ldbm#index objectClass eq overlay ppolicy ppolicy_default "cn=Standard Policy,ou=Policies,dc=foo,dc=bar,dc=edu" ppolicy_use_lockout access to attr=userPassword by self write by anonymous auth by dn.base="cn=Admin,dc=foo,dc=bar,dc=edu" write by dn.base="cn=Manager,dc=foo,dc=bar,dc=edu" write by * none access to * by self write by dn.base="cn=Admin,dc=foo,dc=bar,dc=edu" write by dn.base="cn=Manager,dc=foo,dc=bar,dc=edu" write by * read #database monitor ================================================== 3) Here is the ldap.conf file on the client and server ================================================== # @(#)$Id: ldap.conf,v 1.38 2006/05/15 08:13:31 lukeh Exp $ # # This is the configuration file for the LDAP nameservice # switch library and the LDAP PAM module. # # The man pages for this file are nss_ldap(5) and pam_ldap(5) # # PADL Software # http://www.padl.com # # Your LDAP server. Must be resolvable without using LDAP. # Multiple hosts may be specified, each separated by a # space. How long nss_ldap takes to failover depends on # whether your LDAP client library supports configurable # network or connect timeouts (see bind_timelimit). host 127.0.0.1 # The distinguished name of the search base. base dc=foo,dc=bar,dc=edu # Another way to specify your LDAP server is to provide an # uri with the server name. This allows to use # Unix Domain Sockets to connect to a local LDAP Server. #uri ldap://127.0.0.1/ #uri ldaps://127.0.0.1/ #uri ldapi://%2fvar%2frun%2fldapi_sock/ # Note: %2f encodes the '/' used as directory separator # The LDAP version to use (defaults to 3 # if supported by client library) #ldap_version 3 # The distinguished name to bind to the server with. # Optional: default is to bind anonymously. #binddn cn=proxyuser,dc=example,dc=com # The credentials to bind with. # Optional: default is no credential. #bindpw secret # The distinguished name to bind to the server with # if the effective user ID is root. Password is # stored in /etc/ldap.secret (mode 600) rootbinddn cn=Manager,dc=foo,dc=bar,dc=edu # The port. # Optional: default is 389. port 389 # The search scope. #scope sub #scope one #scope base # Search timelimit #timelimit 30 timelimit 120 # Bind/connect timelimit #bind_timelimit 30 bind_timelimit 120 # Reconnect policy: hard (default) will retry connecting to # the software with exponential backoff, soft will fail # immediately. #bind_policy hard # Idle timelimit; client will close connections # (nss_ldap only) if the server has not been contacted # for the number of seconds specified below. #idle_timelimit 3600 idle_timelimit 3600 # Filter to AND with uid=%s #pam_filter objectclass=account # The user ID attribute (defaults to uid) #pam_login_attribute uid # Search the root DSE for the password policy (works # with Netscape Directory Server) pam_lookup_policy yes # Check the 'host' attribute for access control # Default is no; if set to yes, and user has no # value for the host attribute, and pam_ldap is # configured for account management (authorization) # then the user will not be allowed to login. #pam_check_host_attr yes # Check the 'authorizedService' attribute for access # control # Default is no; if set to yes, and the user has no # value for the authorizedService attribute, and # pam_ldap is configured for account management # (authorization) then the user will not be allowed # to login. #pam_check_service_attr yes # Group to enforce membership of #pam_groupdn cn=PAM,ou=Groups,dc=example,dc=com # Group member attribute #pam_member_attribute uniquemember # Specify a minium or maximum UID number allowed #pam_min_uid 0 #pam_max_uid 0 # Template login attribute, default template user # (can be overriden by value of former attribute # in user's entry) #pam_login_attribute userPrincipalName #pam_template_login_attribute uid #pam_template_login nobody # HEADS UP: the pam_crypt, pam_nds_passwd, # and pam_ad_passwd options are no # longer supported. # # Do not hash the password at all; presume # the directory server will do it, if # necessary. This is the default. #pam_password clear # Hash password locally; required for University of # Michigan LDAP server, and works with Netscape # Directory Server if you're using the UNIX-Crypt # hash mechanism and not using the NT Synchronization # service. #pam_password crypt # Remove old password first, then update in # cleartext. Necessary for use with Novell # Directory Services (NDS) #pam_password clear_remove_old #pam_password nds # RACF is an alias for the above. For use with # IBM RACF #pam_password racf # Update Active Directory password, by # creating Unicode password and updating # unicodePwd attribute. #pam_password ad # Use the OpenLDAP password change # extended operation to update the password. #pam_password exop # Redirect users to a URL or somesuch on password # changes. #pam_password_prohibit_message Please visit http://internal to change your password. # RFC2307bis naming contexts # Syntax: # nss_base_XXX base?scope?filter # where scope is {base,one,sub} # and filter is a filter to be &'d with the # default filter. # You can omit the suffix eg: # nss_base_passwd ou=People, # to append the default base DN but this # may incur a small performance impact. #nss_base_passwd ou=People,dc=example,dc=com?one #nss_base_shadow ou=People,dc=example,dc=com?one #nss_base_group ou=Group,dc=example,dc=com?one #nss_base_hosts ou=Hosts,dc=example,dc=com?one #nss_base_services ou=Services,dc=example,dc=com?one #nss_base_networks ou=Networks,dc=example,dc=com?one #nss_base_protocols ou=Protocols,dc=example,dc=com?one #nss_base_rpc ou=Rpc,dc=example,dc=com?one #nss_base_ethers ou=Ethers,dc=example,dc=com?one #nss_base_netmasks ou=Networks,dc=example,dc=com?ne #nss_base_bootparams ou=Ethers,dc=example,dc=com?one #nss_base_aliases ou=Aliases,dc=example,dc=com?one #nss_base_netgroup ou=Netgroup,dc=example,dc=com?one # Just assume that there are no supplemental groups for these named users nss_initgroups_ignoreusers root,ldap,named,avahi,haldaemon # attribute/objectclass mapping # Syntax: #nss_map_attribute rfc2307attribute mapped_attribute #nss_map_objectclass rfc2307objectclass mapped_objectclass # configure --enable-nds is no longer supported. # NDS mappings #nss_map_attribute uniqueMember member # Services for UNIX 3.5 mappings #nss_map_objectclass posixAccount User #nss_map_objectclass shadowAccount User #nss_map_attribute uid msSFU30Name #nss_map_attribute uniqueMember msSFU30PosixMember #nss_map_attribute userPassword msSFU30Password #nss_map_attribute homeDirectory msSFU30HomeDirectory #nss_map_attribute homeDirectory msSFUHomeDirectory #nss_map_objectclass posixGroup Group #pam_login_attribute msSFU30Name #pam_filter objectclass=User #pam_password ad # configure --enable-mssfu-schema is no longer supported. # Services for UNIX 2.0 mappings #nss_map_objectclass posixAccount User #nss_map_objectclass shadowAccount user #nss_map_attribute uid msSFUName #nss_map_attribute uniqueMember posixMember #nss_map_attribute userPassword msSFUPassword #nss_map_attribute homeDirectory msSFUHomeDirectory #nss_map_attribute shadowLastChange pwdLastSet #nss_map_objectclass posixGroup Group #nss_map_attribute cn msSFUName #pam_login_attribute msSFUName #pam_filter objectclass=User #pam_password ad # RFC 2307 (AD) mappings #nss_map_objectclass posixAccount user #nss_map_objectclass shadowAccount user #nss_map_attribute uid sAMAccountName #nss_map_attribute homeDirectory unixHomeDirectory #nss_map_attribute shadowLastChange pwdLastSet #nss_map_objectclass posixGroup group #nss_map_attribute uniqueMember member #pam_login_attribute sAMAccountName #pam_filter objectclass=User #pam_password ad # configure --enable-authpassword is no longer supported # AuthPassword mappings #nss_map_attribute userPassword authPassword # AIX SecureWay mappings #nss_map_objectclass posixAccount aixAccount #nss_base_passwd ou=aixaccount,?one #nss_map_attribute uid userName #nss_map_attribute gidNumber gid #nss_map_attribute uidNumber uid #nss_map_attribute userPassword passwordChar #nss_map_objectclass posixGroup aixAccessGroup #nss_base_group ou=aixgroup,?one #nss_map_attribute cn groupName #nss_map_attribute uniqueMember member #pam_login_attribute userName #pam_filter objectclass=aixAccount #pam_password clear # Netscape SDK LDAPS #ssl on # Netscape SDK SSL options #sslpath /etc/ssl/certs # OpenLDAP SSL mechanism # start_tls mechanism uses the normal LDAP port, LDAPS typically 636 #ssl start_tls #ssl on # OpenLDAP SSL options # Require and verify server certificate (yes/no) # Default is to use libldap's default behavior, which can be configured in # /etc/openldap/ldap.conf using the TLS_REQCERT setting. The default for # OpenLDAP 2.0 and earlier is "no", for 2.1 and later is "yes". #tls_checkpeer yes # CA certificates for server certificate verification # At least one of these are required if tls_checkpeer is "yes" #tls_cacertfile /etc/ssl/ca.cert #tls_cacertdir /etc/ssl/certs # Seed the PRNG if /dev/urandom is not provided #tls_randfile /var/run/egd-pool # SSL cipher suite # See man ciphers for syntax #tls_ciphers TLSv1 # Client certificate and key # Use these, if your server requires client authentication. #tls_cert #tls_key # Disable SASL security layers. This is needed for AD. #sasl_secprops maxssf=0 # Override the default Kerberos ticket cache location. #krb5_ccname FILE:/etc/.ldapcache # SASL mechanism for PAM authentication - use is experimental # at present and does not support password policy control #pam_sasl_mech DIGEST-MD5

2 1

schema
by John Kellen 18 Jul '08

18 Jul '08

Hello, what schema do i need to have configured in slapd.conf to use this ldif file: *dn: cn=aderaede,ou=People,dc=vub,dc=ac,dc=be objectClass: top objectClass: person objectClass: organizationalPerson objectClass: inetOrgPerson objectClass: posixAccount objectClass: inetLocalMailRecipient objectClass: shadowAccount uid: aderaede sn: *********** givenName: Anouk cn: aderaede userPassword: {crypt}WZpdKybON0LAQ loginShell: /bin/csh uidNumber: 25556 gidNumber: 3294 homeDirectory: /u/aderaede gecos: *************** mail: ************* displayName: *************** ** I have the following configured in slapd.conf *# Schema and objectClass definitions include /etc/ldap/schema/core.schema include /etc/ldap/schema/cosine.schema include /etc/ldap/schema/nis.schema include /etc/ldap/schema/inetorgperson.schema include /etc/ldap/schema/openldap.schemaµ* Thanks J

3 5

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

openldap-technical