1 .TH pam_afs 5 "5 August 2002"
4 pam_afs, pam_afs.so \- pluggable authentication modules for OpenAFS
7 .B pam_afs.so.1, pam_afs.krb.so.1
10 The OpenAFS pluggable authentication module provides module support
11 for authentication, session management, and password management, which
12 coorespond to the auth, session, and password directives in a PAM
13 configuration file, respectively.
17 module additionally keeps users' Kerberos 4 TGT available for users
18 to use in other applications. The
20 module does not do this.
24 module has nothing to do with Kerberos 5 authentication. Users
25 with a Kerberos 5 integrated AFS environment should not use
26 either of these modules, but instead use
31 The following arguments are supported. In parenthesis next to
32 each option are the environments in which it works.
37 to authenticate to other than the local cell.
39 (all) Provide extra debugging information to syslog.
41 (auth) Do not use a fork() when authenticating. Forking is a good idea,
42 because sockets and memory used by the authentication function get
43 cleaned up automatically. This option should only be used if a
44 PAM application fails when a fork() is issued. This option cannot
48 (auth, password) If user root is authenticating, simply return PAM_SUCCESS without
49 any AFS authentication attempt. Presumably, authentication would fall through
50 to a secondary mechanism.
52 (auth) Similar to ignore_root but it allows you to specify a
54 such that any user authenticating with uid less than or equal to
56 will not have AFS authentication performed.
58 (session) Does not destroy a token during logout. This is useful if
59 users have background jobs still running under their PAG that
60 need access to AFS after they log out.
62 (auth, password) Prevents warning from being written to syslog.
64 (auth) Obtains a token without first obtaining a PAG. This is useful for
65 screensavers to update the lifetime of a user's token.
67 (session) Causes AFS tokens to remain for 5 minutes after logout.
68 .IP "remainlifetime lifetime"
69 (session) Specify, in seconds, how long tokens should remain after
72 (auth) If set_token is specified, the token obtained in the authentication
73 phase is not destroyed. Ordinarily, tokens are obtained in the
74 setcred() phase of authentication. For PAM applications which do not
77 directive should be used.
78 .IP setenv_password_expires
79 (auth) Sets the PASSWORD_EXPIRES environment variable to the time when your
80 AFS token will expire.
82 (auth, password) This will first try a password entered to a previous module and if it
83 fails, prompt for the user's AFS password.
86 is the first module called, it will generate a failed login attempt
87 with a NULL password for every user logging in.
89 (auth, password) This option is similar to
91 except that it will not prompt for the user's AFS password if the first
92 password fails. If this option is specified and
94 is the first module listed in the PAM configuration, authentication
99 to exec klog for authentication instead of calling the authentication
100 functions in the AFS libraries directly.
105 This is the PAM configuration file on Solaris systems.
110 These are the PAM configuration files on Linux systems.
113 .I /etc/pam.d/system-auth
115 This file controls all system authentication on many
123 .I /etc/pam.d/system-auth
124 on Linux using OpenAFS:
126 auth required /lib/security/pam_env.so
128 auth sufficient /lib/security/pam_afs.so.1 \\
130 setenv_password_expires ignore_root
132 auth sufficient /lib/security/pam_unix.so likeauth \\
134 nullok try_first_pass
136 auth required /lib/security/pam_deny.so
139 Suggested settings for
142 .I /etc/pam.d/xscreensaver
144 auth sufficient /lib/security/pam_afs.so.1 \\
146 refresh_token ignore_root
148 auth required /lib/security/pam_stack.so \\
154 Charles Clancy <tcc@xauth.net>