openldap-technical

openldap-technical@openldap.org

3 participants
9937 discussions

State of the relay backend and rwm overlay, is it safe?
by Jeffrey Crawford 09 Oct '11

09 Oct '11

Hello, I'm sorry if this is answered somewhere already but I haven't found it. In short we need to re-map some attributes for specific replication schenerios where the replica actually records the data that we've mapped on the master server. Everything works as needed however I did notice that both relay and rwm have been tagged as experimental. This would be used in a production environment so I'm trying to get a sense if I can offer to use these features in our architechture. Or if these backends/overlays are not considered safe to use. I'm using openldap 2.4.26 Thanks Jeffrey

4 4

Re: Patching openldap?
by Christian Manal 09 Oct '11

09 Oct '11

Am 07.10.2011 23:58, schrieb NetNinja: > Ok that's good to know. > I was reading in the book "Solaris 10 System Administration Essential" > and it says on pg 365 that the openldap server needs to be patched so > that the ldapclient init utility will configure properly. > > Do you happen to remeber how you setup the Solaris Native client? This > my current issue, I installed openldap on a RHEL 5.5 server and have all > the Linux servers working with the ldap server but the Solaris servers > won't let me login as a ldap user. I can do a ldapsearch, id, getent and > get info on ldap users. I am in the process of troubleshooting the issue > and I'm not sure what I'm doing wrong? My setup is very basic, no TLS, > uatomount or replication. I will add these later when I know what i'm doing. > > Anyway thanks for your help. If you have any advice on ldapclient setup > let me know. > > On Fri, Oct 7, 2011 at 3:41 PM, Christian Manal > <moenoel(a)informatik.uni-bremen.de > <mailto:moenoel@informatik.uni-bremen.de>> wrote: > > Am 07.10.2011 20:25, schrieb NetNinja: > > Hello, > > I have been reading up on OpenLDAP. I have installed it on RHEL > 5.5 but > > I have seen documention saying that openldap needs to be patched > to work > > with Solaris. Can someone tell me if this still the case and if so > where > > to get the patch. If not any info you can provide wold be great. > > > > Thanks > > > > > > Hi, > > I've been running OpenLDAP on Solaris 10 for years now. It works out of > the tarball, no patches needed. > > > Regards, > Christian Manal > > > > > Here's an example of an ldapclient invocation that works for me: ldapclient manual \ -a authenticationMethod="tls:simple" \ -a credentialLevel="proxy" \ -a defaultSearchBase="dc=example,dc=org" \ -a defaultSearchScope="sub" \ -a defaultServerList="ldap1.example.org,ldap2.example.org" \ -a domainName="example.org" \ -a preferredServerList="ldap1.example.org,ldap2.example.org" \ -a serviceSearchDescriptor="passwd:ou=People,dc=example,dc=org" \ -a serviceSearchDescriptor="group:ou=Group,dc=example,dc=org" \ -a serviceSearchDescriptor="netgroup:ou=Netgroup,dc=example,dc=org" \ -a serviceSearchDescriptor="auto_home:ou=auto_home,ou=Mounts,dc=example,dc=org" \ -a attributeMap="auto_home:automountMapName=ou" \ -a attributeMap="auto_home:automountKey=cn" \ -a proxyDN="uid=proxyauth,ou=people,dc=example,dc=org" \ -a proxyPassword="foobar" Before you invoke that, you need to modify /etc/nsswitch.ldap to your needs (ldapclient will copy that to /etc/nsswitch.conf). You also need to put your TLS certs into /var/ldap in NSS format (you can generate/convert them with certutil[1]) and edit /etc/pam.conf for LDAP authentication. Regards, Christian Manal [1] http://www.mozilla.org/projects/security/pki/nss/tools/certutil.html

2 2

Re: Patching openldap?
by NetNinja 09 Oct '11

09 Oct '11

On Fri, Oct 7, 2011 at 5:47 PM, NetNinja <2bitninja(a)gmail.com> wrote: > > I'm sorry about that. I was reading in the book "Solaris 10 System Administration Essential" and it says on pg 365 that the openldap server needs to be patched so that the ldapclient init utility will configure properly. Most stuff I have read say I need to add these two schemas, solaris and DUAConfigProfile. > > Anyway I'm having issues getting the Solaris servers to work right with the openldap server I installed on a RHEL 5.5 box. The servers can see the data when I do a search and a Id but I can't login with the ldap accouts. > > Thanks for reading my email. > > On Fri, Oct 7, 2011 at 3:31 PM, Quanah Gibson-Mount <quanah(a)zimbra.com> wrote: >> >> --On Friday, October 07, 2011 2:25 PM -0400 NetNinja <2bitninja(a)gmail.com> wrote: >> >>> Hello, >>> I have been reading up on OpenLDAP. I have installed it on RHEL 5.5 but I >>> have seen documention saying that openldap needs to be patched to work >>> with Solaris. Can someone tell me if this still the case and if so where >>> to get the patch. If not any info you can provide wold be great. >> >> Your question is so vague as to be unanswerable. OpenLDAP compiles and runs just fine on Solaris. If you are asking something other than that, than you need to provide more details than vague "I read something somewhere" comments. >> >> --Quanah >> >> -- >> >> Quanah Gibson-Mount >> Sr. Member of Technical Staff >> Zimbra, Inc >> A Division of VMware, Inc. >> -------------------- >> Zimbra :: the leader in open source messaging and collaboration > > > >

3 3

Best way to set up TLS certificates when using syncrepl?
by Bob Fitch 08 Oct '11

08 Oct '11

Hi, I'm trying to figure out the best way to create certificates for LDAPS on servers that replicate to each other. I'm not huge on PKI knowledge, so I'm not exactly sure if what I have is correct. I have two openldap servers that essentially look like this: serverA (provider) ----> serverB (consumer) serverA, serverB and all clients have "URI ldaps://serverA ldaps://serverB" in ldap.conf. I'm trying to make sure all clients can query both serverA and serverB via LDAPS - without extensive re-configuration of ldap.conf should serverA fail. In otherwords, I want the clients to just work, so it doesn't distract the Admin's from fixing serverA. I figured the best way to do this would be to create a single private key on serverA, and from that create certificates for serverA, serverB and any other client. serverB get's a copy of the single private key, just in case. serverA: olcTLSCACertificateFile: /path/to/certificate-authority.crt olcTLSCertificateKeyFile: /path/to/shared-key.key olcTLSCertificateFile: /path/to/serverA-certificate.crt ldap.conf: TLS_CACERT /path/to/certificate-authority.crt serverB: olcTLSCACertificateFile: /path/to/certificate-authority.crt olcTLSCertificateKeyFile: /path/to/shared-key.key olcTLSCertificateFile: /path/to/serverB-certificate.crt ldap.conf: TLS_CACERT /path/to/certificate-authority.crt Does this look correct, given that syncrepl needs to occur between serverA+serverB during normal operation, but LDAPS needs to function correctly between serverB+clients when serverA has failed? Thanks in advance, Bob.

1 0

Overlay memberof does not work with groupOfUniqueNames
by JOSE L MARTINEZ-AVIAL 08 Oct '11

08 Oct '11

Hi, I've an openldap 2.4.23 over RHEL4. I compilled it with the option to use overlay memberof, and it's been working well so far when I created groupOfNames. The issue is that I need to switch to groupOfUniqueNames instead of groupOfNames. When I do that, it seems that the overlay does not work, so I don't receive any group at all when I do a search returning memberof. Is it possible to setup the overlay to do that? Thank you Jose Luis

3 5

ldapbin : Invalid DN Syntax (34)
by Joseph vasanth 07 Oct '11

07 Oct '11

Hi, I am a newbie on openldap. I have just installed openldap on FC11. I am facing issues when i try to bind. When i do an ldapsearch it throws the ldapbin : Invalid DN Syntax (34) error. I have the following information slapd.conf # # See slapd.conf(5) for details on configuration options. # This file should NOT be world readable. # include/etc/openldap/schema/corba.schema include/etc/openldap/schema/core.schema include/etc/openldap/schema/cosine.schema include/etc/openldap/schema/duaconf.schema include/etc/openldap/schema/dyngroup.schema include/etc/openldap/schema/inetorgperson.schema include/etc/openldap/schema/java.schema include/etc/openldap/schema/misc.schema include/etc/openldap/schema/nis.schema include/etc/openldap/schema/openldap.schema include/etc/openldap/schema/ppolicy.schema include/etc/openldap/schema/collective.schema # Allow LDAPv2 client connections. This is NOT the default. allow bind_v2 # Do not enable referrals until AFTER you have a working directory # service AND an understanding of referrals. #referralldap://root.openldap.org pidfile/var/run/openldap/slapd.pid argsfile/var/run/openldap/slapd.args # Load dynamic backend modules: # modulepath/usr/lib/openldap # or /usr/lib64/openldap # moduleload accesslog.la # moduleload auditlog.la # moduleload back_sql.la # moduleload denyop.la # moduleload dyngroup.la # moduleload dynlist.la # moduleload lastmod.la # moduleload pcache.la # moduleload ppolicy.la # moduleload refint.la # moduleload retcode.la # moduleload rwm.la # moduleload syncprov.la # moduleload translucent.la # moduleload unique.la # moduleload valsort.la # The next three lines allow use of TLS for encrypting connections using a # dummy test certificate which you can generate by changing to # /etc/pki/tls/certs, running "make slapd.pem", and fixing permissions on # slapd.pem so that the ldap user or group can read it. Your client software # may balk at self-signed certificates, however. # TLSCACertificateFile /etc/pki/tls/certs/ca-bundle.crt # TLSCertificateFile /etc/pki/tls/certs/slapd.pem # TLSCertificateKeyFile /etc/pki/tls/certs/slapd.pem # Sample security restrictions #Require integrity protection (prevent hijacking) #Require 112-bit (3DES or better) encryption for updates #Require 63-bit encryption for simple bind # security ssf=1 update_ssf=112 simple_bind=64 # Sample access control policy: #Root DSE: allow anyone to read it #Subschema (sub)entry DSE: allow anyone to read it #Other DSEs: #Allow self write access #Allow authenticated users read access #Allow anonymous users to authenticate #Directives needed to implement policy: # access to dn.base="" by * read # access to dn.base="cn=Subschema" by * read # access to * #by self write #by users read #by anonymous auth # # if no access controls are present, the default policy # allows anyone and everyone to read anything but restricts # updates to rootdn. (e.g., "access to * by * read") # # rootdn can always read and write EVERYTHING! ####################################################################### # ldbm and/or bdb database definitions ####################################################################### databasebdb suffix"dc=primecorp,dc=com" checkpoint1024 15 rootdn"cn=Manager,dc=primecorp,dc=com" # Cleartext passwords, especially for the rootdn, should # be avoided. See slappasswd(8) and slapd.conf(5) for details. # Use of strong authentication encouraged. rootpwpassword rootpw{MD5}X03MO1qnZdYdgyfeuILPmQ== # The database directory MUST exist prior to running slapd AND # should only be accessible by the slapd and slap tools. # Mode 700 recommended. directory/var/lib/ldap # Indices to maintain for this database index objectClass eq,pres index ou,cn,mail,surname,givenname eq,pres,sub index uidNumber,gidNumber,loginShell eq,pres index uid,memberUid eq,pres,sub index nisMapName,nisMapEntry eq,pres,sub # Replicas of this database #replogfile /var/lib/ldap/openldap-master-replog #replica host=ldap-1.example.com:389 starttls=critical # bindmethod=sasl saslmech=GSSAPI # authcId=host/ldap-master.example.com(a)EXAMPLE.COM # enable monitoring database monitor access to attrs=userPassword by self write by dn="cn=Manager,dc=primecorp,dc=com" write by anonymous auth by * none # allow onlu rootdn to read the monitor access to * by dn="cn=Manager,dc=primecorp,dc=com" write by self write by * read /etc/ldap.conf # # LDAP Defaults # # See ldap.conf(5) for details # This file should be world readable but not world writable. #BASEdc=example,dc=com #URIldap://ldap.example.com ldap://ldap-master.example.com:666 #SIZELIMIT12 #TIMELIMIT15 #DEREFnever URI ldap://127.0.0.1/ BASE dc=primecorp,dc=com TLS_CACERTDIR /etc/openldap/cacerts /etc/opnldap/ldap.conf # @(#)$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=primecorp,dc=com # 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=example,dc=com # 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_XXXbase?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_passwdou=People, # to append the default base DN but this # may incur a small performance impact. #nss_base_passwdou=People,dc=example,dc=com?one #nss_base_shadowou=People,dc=example,dc=com?one #nss_base_groupou=Group,dc=example,dc=com?one #nss_base_hostsou=Hosts,dc=example,dc=com?one #nss_base_servicesou=Services,dc=example,dc=com?one #nss_base_networksou=Networks,dc=example,dc=com?one #nss_base_protocolsou=Protocols,dc=example,dc=com?one #nss_base_rpcou=Rpc,dc=example,dc=com?one #nss_base_ethersou=Ethers,dc=example,dc=com?one #nss_base_netmasksou=Networks,dc=example,dc=com?ne #nss_base_bootparamsou=Ethers,dc=example,dc=com?one #nss_base_aliasesou=Aliases,dc=example,dc=com?one #nss_base_netgroupou=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,dbus,radvd,tomcat,radiusd,news,mailman,nscd,gdm,polkituser # attribute/objectclass mapping # Syntax: #nss_map_attributerfc2307attributemapped_attribute #nss_map_objectclassrfc2307objectclassmapped_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 uri ldap://127.0.0.1/ ssl no tls_cacertdir /etc/openldap/cacerts pam_password md5 base.ldif # create new dn: dc=primecorp,dc=com objectClass: dcObject objectClass: organization o: primecorp Organization dc: primecorp dn: cn=Manager,dc=primecorp,dc=com objectClass: organizationalRole cn: manager dn: ou=People,dc=primecorp,dc=com objectClass: organizationalUnit ou: People dn: ou=Group,dc=primecorp,dc=com objectClass: organizationalUnit ou: Group ldapsearch -x -h 10.127.1.146 -b "dc=primecorp,dc=com" -D 'admin(a)primecorp.com' -W "cn=admin" Enter LDAP Password: ldap_bind: Invalid DN syntax (34) additional info: invalid DN I have installed and the installation went fine. but ldapsearch keeps giving the same error i also tried other combinations on the dn like adding a ou=Peopledc=primecorp,dc=com, many other combinations but i stll kept hitting the same error or "invalid credentials". I completley stuck as to whether i am putting the correct information.I am not able to see what is exactly wrong with the config. I am using Fedora Core 11 by the way. If someone could please help me with this i would be so appreciative, LDAP looks so easy to set up yet there is something probably so small preventing it being set up correctly. if you need any more information on this just ask me. Regards Joseph

3 2

bind using CN instead of UID
by Craig White 07 Oct '11

07 Oct '11

Obviously there is something that I don't understand because I would expect to be able to bind using CN as well as UID attribute... version: 2.4.21-0ubuntu5.5 ***** this as you can see works ***** # ldapsearch -x -D 'uid=cwhite,ou=people,dc=ttinet,dc=local' -W '(uid=cwhite)' uid, cn Enter LDAP Password: # extended LDIF # # LDAPv3 # base <dc=ttinet,dc=local> (default) with scope subtree # filter: (uid=cwhite) # requesting: uid, cn # # cwhite, people, ttinet.local dn: uid=cwhite,ou=people,dc=ttinet,dc=local cn: Craig White # search result search: 2 result: 0 Success # numResponses: 2 # numEntries: 1 ***** same as above but using cn instead of uid ***** # ldapsearch -x -D 'cn=Craig White,ou=people,dc=ttinet,dc=local' -W '(uid=cwhite)' uid, cn Enter LDAP Password: ldap_bind: Invalid credentials (49) I have to believe that if this is an ACL issue, then the very first rule is the problem... olcAccess: {0}to attrs=userPassword,shadowLastChange by dn.exact="uid=administ rator,ou=people,dc=ttinet,dc=local" write by self write by anonymous auth by * none What is it that I am missing? -- Craig White ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ craig.white(a)ttiltd.com 1.800.869.6908 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ www.ttiassessments.com Need help communicating between generations at work to achieve your desired success? Let us help!

4 4

Patching openldap?
by NetNinja 07 Oct '11

07 Oct '11

Hello, I have been reading up on OpenLDAP. I have installed it on RHEL 5.5 but I have seen documention saying that openldap needs to be patched to work with Solaris. Can someone tell me if this still the case and if so where to get the patch. If not any info you can provide wold be great. Thanks

4 3

Re: Ldap logs accounting
by Hugo Deprez 07 Oct '11

07 Oct '11

Hello, thank you that was exactly what I was looking for. Does anyone know a software such as a web interface, which will be able to read the data from the accesslog base and display them in a more friendly way ? Regards, Hugo On 6 October 2011 04:55, Quanah Gibson-Mount <quanah(a)zimbra.com> wrote: > --On Wednesday, October 05, 2011 11:41 AM +0200 Hugo Deprez > <hugo.deprez(a)gmail.com> wrote: > >> Dear community, >> >> I am currently using openldap 2.4.23-3 on Debian Lenny. I need to be >> able to log all the change made on the directory. >> For exemple if a account is delete I would like to log who did it and >> at what time. >> I want to do some accounting. >> >> Do you know how I could do that ? I didn't found anything on google. > > man slapo-accesslog > > --Quanah > > -- > > Quanah Gibson-Mount > Sr. Member of Technical Staff > Zimbra, Inc > A Division of VMware, Inc. > -------------------- > Zimbra :: the leader in open source messaging and collaboration >

3 4

Re: Unable to create home directory (LDAP Authentication)
by vijay s sheelavantar 07 Oct '11

07 Oct '11

Hi,I am sorry for the inconvenience caused due to the unreadable format. On fedora I don't have this file. /etc/pam.d/common-session. Below logs for your reference. in the log file /var/log/messages i found the following error Oct  6 13:37:56 localhost setroubleshoot: SELinux is preventing sshd (sshd_t) "write" to ./home (home_root_t). For complete SELinux messages. run sealert -l ecdf3def-df6e-4d5b-851b-4e9bf155e57d and in the log file /var/log/secure below error found. Oct  6 15:14:04 localhost sshd[3844]: pam_unix(sshd:session): session closed for user kimOct  6 15:14:07 localhost sshd[3900]: Accepted password for kim from 10.254.194.148 port 57079 ssh2Oct  6 15:14:07 localhost sshd[3900]: pam_mkhomedir(sshd:session): unable to create directory /home/kim: Permission deniedOct  6 15:14:07 localhost sshd[3900]: pam_unix(sshd:session): session opened for user kim by (uid=0)Oct  6 15:14:07 localhost sshd[3900]: error: ssh_selinux_setup_pty: security_compute_relabel: Invalid argument please help me to find a solution. Warm Regards,Vijay S.

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

openldap-technical