9 More Discussions You Might Find Interesting
1. Solaris
I have very limited knowledge on LDAP configuration and have been trying fix one issue, but unsuccessful.
The server, I am working on, is Solaris-10 zone. sudoers is configured on LDAP (its not on local server). I have access to login directly on server with root, but somehow sudo is not working... (9 Replies)
Discussion started by: solaris_1977
9 Replies
2. Red Hat
Hey guys
iīve one big problem with nscd.conf this donīt work i tried many examples of configuration the nscd.conf simply donīt work when i stop the ldap server i try access by ssh on the client i canīt make logon.
And the database on /var/db/nscd donīt work.
follows below the conf of... (0 Replies)
Discussion started by: paulo_eduardo
0 Replies
3. UNIX for Advanced & Expert Users
Hi
I am searching a tool like "LDAP Administrator 2011.1"/ "LDAP-SQL" but for the CLI.
Wish to use LDAP-SQL in scripts (non Windows GUI environment)
http://ldapadministrator.com/resources/english/2011.1/images/sqlquery_large.png
Softerra LDAP Administrator 2011.1 - What's New
OS is... (2 Replies)
Discussion started by: slashdotweenie
2 Replies
4. AIX
Hello.
I'm experiencing a frustrating issue.
I'm using an old, unsupported terminal client (QVT) with AIX 6.1 using ssh2. I've come up with some stty settings that allow full usage of the system but to do so I've had to set "igncr". While this works fine once the user is logged in there are... (12 Replies)
Discussion started by: RedCabbage
12 Replies
5. OS X (Apple)
Hi All,
I want to login to CVS using terminal. I am executing the following command in the terminal :-
export CVSROOT=: pserver:ags_rd@istcvs.corp.apple.com:/istcvs/CVSHOME
cvs login
But i get the following error :
Afreens-iMac:buildTest Afreen$ export CVSROOT=:... (1 Reply)
Discussion started by: Afreen
1 Replies
6. Shell Programming and Scripting
Hi All,
I want to login to CVS using terminal. I am executing the following command in the terminal :-
export CVSROOT=: pserver:ags_rd@istcvs.corp.apple.com:/istcvs/CVSHOME
cvs login
But i get the following error :
Afreens-iMac:buildTest Afreen$ export CVSROOT=:... (3 Replies)
Discussion started by: Afreen
3 Replies
7. Shell Programming and Scripting
Hello All
Nice to meet you all here in this forum,
it's my 1rst time here
i'm asking about a little issue that i face
i added a ksh script that echo " please insert your name " and store the output to a login.log file.
the script is working fine with normal telnet
but Xstart is not working... (8 Replies)
Discussion started by: islam.said
8 Replies
8. UNIX for Advanced & Expert Users
Hi folks,
we have a very heterogenous server environment. There are also lots of AIX and Linux servers which usually have different login shells and all servers have to be integrated into LDAP. The LDAP Meta Directory is hosted by a Novell eDirectory.
On our Linux boxes it is usually bash, on... (5 Replies)
Discussion started by: zaxxon
5 Replies
9. Web Development
Hello,
I have created a web page on a server using apache and added .htaccess and .htpasswd in the folder for authentification.
I was wondering if there was anyway to tie-in the login for this page with the login used to logon to the server.
i.e. the same login info. is used for both,... (2 Replies)
Discussion started by: WhotheWhat
2 Replies
pam_ldap(5) pam_ldap(5)
NAME
pam_ldap - authentication and account management PAM module for LDAP
SYNOPSIS
/usr/lib/security/pam_ldap.so.1
The pam_ldap module implements pam_sm_authenticate() and pam_sm_acct_mgmt(), the functions that provide functionality for the PAM authenti-
cation and account management stacks. The pam_ldap module ties the authentication and account management functionality to the functionality
of the supporting LDAP server. For authentication, pam_ldap can authenticate the user directly to any LDAP directory server by using any
supported authentication mechanism, such as DIGEST-MD5. However, the account management component of pam_ldap will work only with the Sun
Java System Directory Server. The server's user account management must be properly configured before it can be used by pam_ldap. Refer to
the Sun Java System Directory Server Administration Guide for information on how to configure user account management, including password
and account lockout policy.
pam_ldap must be used in conjunction with the modules that support the UNIX authentication, password, and account management, which are
pam_authtok_get(5), pam_passwd_auth(5), pam_unix_account(5), and pam_unix_auth(5). pam_ldap is designed to be stacked directly below these
modules. If other modules are designed to be stacked in this manner, the modules can be stacked below the pam_ldap module. The section
shows how the UNIX modules are stacked with pam_ldap. When stacked together, the UNIX modules are used to control local accounts, such as
root. pam_ldap is used to control network accounts, that is, LDAP users. For the stacks to work, pam_unix_auth, pam_unix_account, and
pam_passwd_auth must be configured with the binding control flag and the server_policy option. This configuration allows local account
override of a network account.
LDAP Authentication Module
The LDAP authentication module verifies the identity of a user. The pam_sm_authenticate(3PAM) function uses the password entered by the
user to attempt to authenticate to the LDAP server. If successful, the user is authenticated. See for information on password prompting.
The authentication method used is either defined in the client profile , or the authentication method is configured by using the ldap-
client(1M) command. To determine the authentication method to use, this module first attempts to use the authentication method that is
defined, for service pam_ldap, for example, serviceAuthenticationMethod:pam_ldap:sasl/DIGEST-MD5. If no authentication method is defined,
pam_ldap uses the default authentication method. If neither are set, the authentication fails. This module skips the configured authentica-
tion method if the authentication method is set to none.
The following options may be passed to the LDAP service module:
debug
syslog(3C) debugging information at LOG_DEBUG level.
nowarn
Turn off warning messages.
These options are case sensitive, and the options must be used exactly as presented here.
LDAP Account Management Module
The LDAP account management module validates the user's account. The pam_sm_acct_mgmt(3PAM) function authenticates to the LDAP server to
verify that the user's password has not expired, or that the user's account has not been locked. The following options may be passed to the
LDAP service module:
debug
syslog(3C) debugging information at LOG_DEBUG level.
nowarn
Turn off warning messages.
These options are case sensitive, and the options must be used exactly as presented here.
LDAP Password Management Module
LDAP password management is no longer supported by pam_ldap. Use pam_authtok_store(5) instead of pam_ldap for password change. pam_auth-
tok_store(5) handles both the local and LDAP accounts and updates the passwords in all the repositories configured by nsswitch.conf(4).
The authentication service returns the following error codes:
PAM_SUCCESS Authentication successful
PAM_MAXTRIES Maximum number of authentication attempts exceeded
PAM_AUTH_ERR Authentication failure
PAM_USER_UNKNOWN No account present for user
PAM_BUF_ERR Memory buffer error
PAM_SYSTEM_ERR System error
PAM_IGNORE User's account inactivated
The account management service returns the following error codes:
PAM_SUCCESS User allowed access to account
PAM_NEW_AUTHTOK_REQD New authentication token required
PAM_ACCT_EXPIRED User account has expired
PAM_PERM_DENIED User denied access to account at this time
PAM_USER_UNKNOWN No account present for user
PAM_BUF_ERROR Memory buffer error
PAM_SYSTEM_ERR System error
Example 1: Using pam_ldap With Authentication
The following is a configuration for the login service when using pam_ldap. The service name login can be substituted for any other authen-
tication service such as dtlogin or su. Lines that begin with the # symbol are comments and are ignored.
# Authentication management for login service is stacked.
# If pam_unix_auth succeeds, pam_ldap is not invoked.
# The control flag "binding" provides a local overriding
# remote (LDAP) control. The "server_policy" option is used
# to tell pam_unix_auth.so.1 to ignore the LDAP users.
login auth requisite pam_authtok_get.so.1
login auth required pam_dhkeys.so.1
login auth required pam_unix_cred.so.1
login auth binding pam_unix_auth.so.1 server_policy
login auth required pam_ldap.so.1
Example 2: Using pam_ldap With Account Management
The following is a configuration for account management when using pam_ldap. Lines that begin with the # symbol are comments and are
ignored.
# Account management for all services is stacked
# If pam_unix_account succeeds, pam_ldap is not invoked.
# The control flag "binding" provides a local overriding
# remote (LDAP) control. The "server_policy" option is used
# to tell pam_unix_account.so.1 to ignore the LDAP users.
other account requisite pam_roles.so.1
other account binding pam_unix_account.so.1 server_policy
other account required pam_ldap.so.1
Example 3: Using pam_authtok_store With Password Management For Both Local and LDAP Accounts
The following is a configuration for password management when using pam_authtok_store. Lines that begin with the # symbol are comments and
are ignored.
# Password management (authentication)
# The control flag "binding" provides a local overriding
# remote (LDAP) control. The server_policy option is used
# to tell pam_passwd_auth.so.1 to ignore the LDAP users.
passwd auth binding pam_passwd_auth.so.1 server_policy
passwd auth required pam_ldap.so.1
# Password management (updates)
# This updates passwords stored both in the local /etc
# files and in the LDAP directory. The "server_policy"
# option is used to tell pam_authtok_store to
# follow the LDAP server's policy when updating
# passwords stored in the LDAP directory
other password required pam_dhkeys.so.1
other password requisite pam_authtok_get.so.1
other password requisite pam_authtok_check.so.1
other password required pam_authtok_store.so.1 server_policy
/var/ldap/ldap_client_file The LDAP configuration files of the client. Do not manually modify these files, as these files may not be
/var/ldap/ldap_client_cred human readable. Use ldapclient(1M) to update these files.
/etc/pam.conf PAM configuration file.
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Interface Stability |Evolving |
+-----------------------------+-----------------------------+
|MT-Level |MT-Safe with exceptions |
+-----------------------------+-----------------------------+
ldap(1), idsconfig(1M), ldap_cachemgr(1M), ldapclient(1M), libpam(3LIB), pam(3PAM), pam_sm_authenticate(3PAM), pam_sm_chauthtok(3PAM),
pam_sm_close_session(3PAM), pam_sm_open_session(3PAM), pam_sm_setcred(3PAM), syslog(3C), pam.conf(4), attributes(5), pam_authtok_check(5),
pam_authtok_get(5), pam_authtok_store(5), pam_passwd_auth(5), pam_unix_account(5), pam_unix_auth(5)
The interfaces in libpam(3LIB) are MT-Safe only if each thread within the multi-threaded application uses its own PAM handle.
The previously supported use_first_pass and try_first_pass options are obsolete in this version, are no longer needed, can safely be
removed from pam.conf(4), and are silently ignored. They might be removed in a future release. Password prompting must be provided for by
stacking pam_authtok_get(5) before pam_ldap in the auth and password module stacks and pam_passwd_auth(5) in the passwd service auth stack
(as described in the section). The previously supported password update function is replaced in this release by the previously recommended
use of pam_authtok_store with the server_policy option (as described in the section).
The functions: pam_sm_setcred(3PAM), pam_sm_chauthtok(3PAM), pam_sm_open_session(3PAM), and pam_sm_close_session(3PAM) do nothing and
return PAM_IGNORE in pam_ldap.
10 May 2005 pam_ldap(5)
