|
From: Jamie C. <jca...@we...> - 2006-02-21 05:51:11
|
Which Linux distributon are you using there? - Jamie On 20/Feb/2006 23:37 Khan, Mohammed [SMO] wrote .. > I not able to find the file in my server, I can you pls send me the file > and I can put it in my server. Thanks. > > -----Original Message----- > From: web...@li... > [mailto:web...@li...]On Behalf Of Jamie > Cameron > Sent: Sunday, February 19, 2006 6:39 AM > To: web...@li... > Subject: RE: [webmin-l] Webmin Servers, Broadcast/scan > > > Hi Mohammed, > That is not the correct file, sorry. The one you attached is for the NSS-LDAP > configuration, but there is also a separate file for PAM-LDAP configuration. > I am not sure where it would be located on your system though - it varies > from one Linux distribution to another. > > - Jamie > > -----Original Message----- > > From: "Khan, Mohammed [SMO]" <MK...@fr...> > Subj: RE: [webmin-l] Webmin Servers, Broadcast/scan > Date: Sat 18 Feb 2006 5:55 am > Size: 2K > To: <web...@li...> > > Morning Jamie, > I am attaching my ldap.conf file please check and let me know what I am > doing wrong. If I an able the bindpw I am not able to login to usermin. > Please check if the way I have set it up is correct. Do I create a file > /etc/ldap.secret and copy the line from ldap.conf file. Please let me > know > # @(#)$Id: ldap.conf,v 1.27 2003/01/17 21:37:12 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 > host dublx06.noam.corp.frk.com > > # The distinguished name of the search base. > #base dc=example,dc=com > #base dc=people,dc=noam,dc=corp,dc=frk,dc=com > base dc=noam,dc=corp,dc=frk,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 > #binddn cn=Directory Manager > > # 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 > rootbinddn cn=Directory Manager > > # The port. > # Optional: default is 389. > #port 389 > > # The search scope. > #scope sub > #scope one > #scope base > > # Search timelimit > #timelimit 30 > > # Bind timelimit > #bind_timelimit 30 > > # 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 > pam_filter objectclass=posixAccount > > # 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) > > --- message truncated --- |