T
titi-Afpa

  • 20 avr. 2011
  • Inscrit 10 avr. 2011
  • 0 meilleure réponse
  • Voici, mon Slapd.conf :

    #

    # See slapd.conf(5) for details on configuration options.

    # This file should NOT be world readable.

    #

    include /etc/openldap/schema/core.schema

    include /etc/openldap/schema/cosine.schema

    include /etc/openldap/schema/inetorgperson.schema

    include /etc/openldap/schema/nis.schema

    include /etc/openldap/schema/samba.schema

    include /etc/openldap/schema/collective.schema

    include /etc/openldap/schema/corba.schema

    include /etc/openldap/schema/duaconf.schema

    include /etc/openldap/schema/dyngroup.schema

    include /etc/openldap/schema/java.schema

    include /etc/openldap/schema/misc.schema

    include /etc/openldap/schema/openldap.schema

    # include /etc/openldap/schema/pmi.schema

    include /etc/openldap/schema/ppolicy.schema



    # schemacheck on



    # 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.

    # referral ldap://root.openldap.org



    pidfile /var/run/openldap/slapd.pid

    argsfile /var/run/openldap/slapd.args



    # Load dynamic backend modules:

    # modulepath /usr/sbin/openldap

    # moduleload back_bdb.la

    # moduleload back_ldap.la

    # moduleload back_ldbm.la

    # moduleload back_passwd.la

    # moduleload back_shell.la



    # The next three lines allow use of TLS for encrypting connections

    # using a

    # dummy test certificate which you can generate by changing to

    # /usr/share/ssl/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.



    #TLSCertificateFile /etc/pki/certs/slapd/titiplot6_cert.pem

    #TLSCertificateKeyFile /etc/pki/certs/slapd/titiplot6_key.pem

    #TLSCACertificateFile /etc/pki/certs/slapd/AFPACM_Cacert.pem

    #TLSCipherSuite :SSLv3

    #TLSVerifyClient never



    # 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

    #######################################################################



    database bdb

    # Racine de l' annuaire

    suffix o=AFPA,c=FR

    # Identifiant du gestionnaire de la base

    rootdn cn=titi,o=AFPA,c=FR

    # Mot de passe du gestionnaire de la base.

    # rootpw {crypt}ijFYNcSNctBYg

    # 1234

    rootpw {CRYPT}BZXDDqoolbuGo



    # 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"

    lastmod on



    # Indices to maintain for this database

    index objectClass eq,pres

    index ou,cn,sn,mail,givenname eq,pres,sub

    index uidNumber,gidNumber,memberUid eq,pres

    index loginShell eq,pres

    ## required to support pdb_getsampwnam

    index uid pres,sub,eq

    ## required to support pdb_getsambapwrid()

    index displayName pres,sub,eq

    index nisMapName,nisMapEntry eq,pres,sub

    index sambaSID eq

    index sambaPrimaryGroupSID eq

    index sambaDomainName eq

    index default sub



    #######################################################################

    # Définitions des listes de contrôles d'accès (ACL)

    #######################################################################



    # access to attrs=userPassword,sambaLMPassword,sambaNTPassword

    # by dn.base="cn=titi,ou=tsrit7,dc=AFPA,dc=FR" write

    # by anonymous auth

    # by self write

    # by * none



    # access to dn.subtree="ou=tsrit7,dc=AFPA,dc=FR"

    # by self write

    # by * read
  • Dans /var/log/messages aucun message concernant ldap.

    Mais j'ai trouver que le système gère slapd.d, il se sert de fichier ldif pour fonctionner, et que l'on peu convertir l'ancien fichier Slapd.conf par la commande :slaptest –f /etc/openldap/slapd.conf –F /etc/openldap/slapd.d.

    Je continue mes recherche sur le sujet.

    Merci pour votre aide
  • De quelle logs parles tu (nom des fichiers ) ?

    Merci
  • Si je supprime le slapd.d en laissant le slapd.conf dans /etc/openldap , et que je démarre le service par : service slapd start, je n'ai aucun message d'erreur mais celui-ci ne démarre pas.
  • Bonjour,

    Je galère depuis 2 semaines sur la nouvelle version de Ldap 2.4.23.

    Je n'arrive pas à me connecter au serveur avec le mot de passe inclus dans slapd.conf, quand j'interoge la base sa me met le message : invalid credetials (49).

    Je suis à court d'idées, j'ai essayer plusieur méthode dont celle cité plus bas de suprimer le répertoire slapd.d, mais rien n'y fait.

    Pour la suppression du répertoire slapd.d, si je fait la manipulation le service ne démarre plus.

    Donc ma question est la suivante, dans cette nouvelle version ou le programme ldap va t'il rechercher ces informations (mots de pass, rotdn), sachant qu'il n'utilise plus le slapd.conf ?.

    Merci pour votre réponse

    Cordialement