ldap-server unter fedora core 5 einrichten

Dieses Thema im Forum "RedHat,Fedora & CentOS" wurde erstellt von gnoovy, 13.04.2006.

  1. gnoovy

    gnoovy Eroberer

    Dabei seit:
    20.02.2004
    Beiträge:
    73
    Zustimmungen:
    0
    hi leutz,


    bin grad an einer ldap-server-konfiguration drann. Dieser soll später Sambaauthentifizierung übernehmen können. Leider kann ich keine Daten dem Ldap-Server hinzufügen. Es kommt immer die Fehlermeldung invalid credentials (49). Was kann das sein?


    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

    # 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/lib/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
    # /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 * write
    # 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 ldbm
    suffix "dc=net,dc=local"
    rootdn "cn=Manager,dc=net,dc=local"
    # Cleartext passwords, especially for the rootdn, should
    # be avoided. See slappasswd(8) and slapd.conf(5) for details.
    # Use of strong authentication encouraged.
    rootpw secret
    # rootpw {crypt}ijFYNcSNctBYg

    # 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@EXAMPLE.COM


    ******************************


    ldap.conf


    *********************


    #
    # LDAP Defaults
    #

    # See ldap.conf(5) for details
    # This file should be world readable but not world writable.

    BASE dc=net,dc=local
    HOST localhost
    URI ldap://localhost

    #SIZELIMIT 12
    #TIMELIMIT 15
    #DEREF never


    ************************



    mit ldapadd -x -D cn=Manager,dc=net,dc=local -w -f <name>.ldif versuche ich die Daten aufzunehmen



    <name>.ldif


    **********************


    # Die Organisation Net.local


    dn: dc=net,dc=local
    objectClass: dcObject
    objectClass: organization
    o: Net.local
    dc: net


    # Die Organisationseinheit der Samausers

    dn: ou=samba,dc=net,dc=local
    objectClass: organizationalUnit
    ou: samba


    *****************************



    Hoffe ihr seht den Fehler



    greetz
    gnoovy
     
  2. Anzeige

    Schau dir mal diese Kategorie an. Dort findest du bestimmt etwas.
    Registrieren bzw. einloggen, um diese und auch andere Anzeigen zu deaktivieren
  3. #2 Snowman, 13.04.2006
    Snowman

    Snowman Linux User

    Dabei seit:
    22.03.2006
    Beiträge:
    58
    Zustimmungen:
    0
    mit ldapadd -x -D cn=Manager,dc=net,dc=local -w -f <name>.ldif versuche ich die Daten aufzunehmen

    Ich hoffe du benutzt "-W" statt "-w", weil mit klein w versucht er das Password aus der passwd zu holen, und ich glaube nicht das dort das passwort "secret" drinne ist.:D
     
  4. gnoovy

    gnoovy Eroberer

    Dabei seit:
    20.02.2004
    Beiträge:
    73
    Zustimmungen:
    0
    hi leutz,


    ja mache ich. I kapier des selber net. Was läuft da no flasch. Gibts da irgendwie wo anders no Passworteinrichtungen, bei denen i da was ändern muss?



    greetz
    gnoovy
     
  5. #4 hoernchen, 13.04.2006
    hoernchen

    hoernchen UBERgarstiges nagetier

    Dabei seit:
    17.02.2005
    Beiträge:
    1.081
    Zustimmungen:
    0
  6. #5 gnoovy, 13.04.2006
    Zuletzt bearbeitet: 14.04.2006
    gnoovy

    gnoovy Eroberer

    Dabei seit:
    20.02.2004
    Beiträge:
    73
    Zustimmungen:
    0
    hi des blick i jetzt net. Der hat doch versucht einen ldap mit einer anderen Domäne aufzunehmen, als er tatsächlich eingegeben hat. Des Problem hab i doch net. Oder was übersehen?

    sorry


    hab noch in der /etc nommel ne ldap.conf gesehen. Habe angepasst, aber geht trotzdem no net. Vielleicht findet ihr no was?


    /etc/ldap.conf


    *********************


    # @(#)$Id: ldap.conf,v 1.36 2005/03/23 08:29:59 lukeh Exp $
    #
    # This is the configuration file for the LDAP nameservice
    # switch library and the LDAP PAM module.
    #
    # 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=net,dc=local

    # 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=Manager,dc=net,dc=local

    # 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=net,dc=local

    # The port.
    # Optional: default is 389.
    #port 389

    # The search scope.
    #scope sub
    #scope one
    scope base

    # Search timelimit
    #timelimit 30

    # Bind/connect timelimit
    #bind_timelimit 30

    # 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

    # 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.
    #
    # If you are using XAD, you can set pam_password
    # to racf, ad, or exop. Make sure that you have
    # SSL enabled.

    # 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

    # 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/cert7.db

    # 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


    ************************************



    grüßle
    gnoovy
     
  7. Anzeige

    Vielleicht findest du HIER Antworten.
    Registrieren bzw. einloggen, um diese und auch andere Anzeigen zu deaktivieren
  8. Pudi

    Pudi Grünschnabel

    Dabei seit:
    07.11.2006
    Beiträge:
    1
    Zustimmungen:
    0
    gleiches prob

    Also ich bin jetzt schon ne ganze weile auf der suche na dem problem wie es oben beschreiben wurde. Ich habe mich an das howto gehalten: http://www.heise.de/ix/artikel/2002/04/148/

    vorher habe ich den samba installiert, na folgendem howto: http://www.debianhowto.de/doku.php/de:howtos:sarge:samba3_pdc

    es ist zwar ein debian howto, aber es funzt trotzdem under Fedora 3 Core5

    Ich versuche also auch ein Samba mit LDAP aufzusetzen und scheitre an dem punkt, wo man die *.ldif in das ldap einfügt. Mit der Fehlermeldung: ldap_bind: Invalid credentials (49)

    Wäre echt schön wenn mir jemand helfen kann.
     
  9. #7 horicen, 23.11.2006
    horicen

    horicen Grünschnabel

    Dabei seit:
    10.11.2006
    Beiträge:
    1
    Zustimmungen:
    0
    Hatte auch das Problem, hatte aller dings in den HOWTOs eine Zeile übersehen, die dem LDAP-Server die Config bekannt macht. Lautet wie folgt:

    su root -c /usr/lib/openldap/slapd -f /etc/openldap/slapd.conf
     
Thema:

ldap-server unter fedora core 5 einrichten

Die Seite wird geladen...

ldap-server unter fedora core 5 einrichten - Ähnliche Themen

  1. Dringend: Samba-Server zerstört Konfiguration des LDAP-Servers. Anonymer Zugang weg.

    Dringend: Samba-Server zerstört Konfiguration des LDAP-Servers. Anonymer Zugang weg.: Hey Leute, hoffe das ist das richtige Forum, brauche allerdings dringend Hilfe! Haben in der Schule den sogenannten Open School Server (basiert...
  2. LDAP-Server startet nicht

    LDAP-Server startet nicht: Hallo, nach der Konfiguration von OpenLDAP und (bereits mehrmaligen) Startversuchen des Servers erscheint die Zeile: Starting ldap-server...
  3. sambaSID in bestehenden LDAP-Server einbinden

    sambaSID in bestehenden LDAP-Server einbinden: Moin moin erst mal, ich hab ein kleines, vielleicht auch ein grosses Problem. Ich hab in der letzten Woche ein LDAP Server aufgesetzt und...
  4. Update auf Apache >=2.4.12 unter Debian Jessie

    Update auf Apache >=2.4.12 unter Debian Jessie: Hi, aufgrund eines Bugs in Apache 2.4 benötige ich zum Deployment von Seafile unter Debian Jessie das Paket apache2 in der Version >= 2.4.12...
  5. Was mache ich falsch? Tiniywm und Mate Install unter OpenBSD

    Was mache ich falsch? Tiniywm und Mate Install unter OpenBSD: Hallo, # make tiny make: don't know how to make tiny Stop in /root/Downloads/tiny/tinywm-1.3 # make tinywm cc -O2 -pipe -o tinywm tinywm.c...