| 1 |
The module takes a number of configuration options. Password changing |
| 2 |
is not implemented, as the RADIUS protocol does not support it. |
| 3 |
|
| 4 |
The pam configuration can be: |
| 5 |
... |
| 6 |
auth sufficient pam_radius_auth.so [options] |
| 7 |
... |
| 8 |
account sufficient pam_radius_auth.so |
| 9 |
|
| 10 |
--------------------------------------------------------------------------- |
| 11 |
|
| 12 |
The 'options' section is optional, and can contain one or more of |
| 13 |
the following strings. Note that not all of these options are |
| 14 |
relevant in for all uses of the module. |
| 15 |
|
| 16 |
debug - print out extensive debugging information via pam_log. |
| 17 |
These messages generally end up being handled by |
| 18 |
syslog(), and go to /var/log/messages. Depending on |
| 19 |
your host operating system, the log messages may be |
| 20 |
elsewhere. |
| 21 |
You should generally use the debug option when first |
| 22 |
trying to install the module, as it will help |
| 23 |
enormously in tracking down problems. |
| 24 |
|
| 25 |
use_first_pass - Instead of prompting the user for a password, retrieve |
| 26 |
the password from the previous authentication module. |
| 27 |
If the password does not exist, return failure. |
| 28 |
If the password exists, try it, returning success/failure |
| 29 |
as appropriate. |
| 30 |
|
| 31 |
try_first_pass - Instead of prompting the user for a password, retrieve |
| 32 |
the password from the previous authentication module. |
| 33 |
If the password exists, try it, and return success if it |
| 34 |
passes. |
| 35 |
If there was no previous password, or the previous password |
| 36 |
fails authentication, prompt the user with |
| 37 |
"Enter RADIUS password: ", and ask for another password. |
| 38 |
Try this password, and return success/failure as appropriate. |
| 39 |
|
| 40 |
This is the default for authentication. |
| 41 |
|
| 42 |
skip_passwd - Do not prompt for a password, even if there was none |
| 43 |
retrieved from the previous layer. |
| 44 |
Send the previous one (if it exists), or else send a NULL |
| 45 |
password. |
| 46 |
If this fails, exit. |
| 47 |
If an Access-Challenge is returned, display the challenge |
| 48 |
message, and ask the user for the response. |
| 49 |
Return success/failure as appropriate. |
| 50 |
|
| 51 |
The password sent to the next authentication module will |
| 52 |
NOT be the response to the challenge. If a password from |
| 53 |
a previous authentication module exists, it is passed on. |
| 54 |
Otherwise, no password is sent to the next module. |
| 55 |
|
| 56 |
conf=foo - set the configuration filename to 'foo'. |
| 57 |
Default is /etc/pam_radius_auth.conf |
| 58 |
|
| 59 |
client_id=bar - send a NAS-Identifier RADIUS attribute with string |
| 60 |
'bar'. If the client_id is not specified, the PAM_SERVICE |
| 61 |
type is used instead. ('login', 'su', 'passwd', etc.) |
| 62 |
This feature may be disabled by using 'client_id='. |
| 63 |
i.e. A blank client ID. |
| 64 |
|
| 65 |
retry=# - How many times to re-send a packet if there is no |
| 66 |
response. Once the retry count has been reached, |
| 67 |
the module fails, and PAM continues to the next module. |
| 68 |
|
| 69 |
use_authtok - force the use of a previously entered password. |
| 70 |
This is needed for pluggable password strength checking |
| 71 |
i.e. try cracklib to be sure it's secure, then go update |
| 72 |
the RADIUS server. |
| 73 |
|
| 74 |
ruser - If PAM_USER is root, Use the value of PAM_RUSER instead |
| 75 |
of PAM_USER to determine the username to authenticate via |
| 76 |
RADIUS. This is to allow 'su' to act like 'sudo'. |
| 77 |
|
| 78 |
localifdown - This option tells pam_radius to return PAM_IGNORE instead |
| 79 |
of PAM_AUTHINFO_UNAVAIL if RADIUS auth failed due to |
| 80 |
network unavailability. PAM_IGNORE tells the pam stack |
| 81 |
to continue down the stack regardless of the control flag. |
| 82 |
|
| 83 |
prompt=string - Specifies the prompt, without the ': ', that PAM should |
| 84 |
display when prompting for the password. This is useful |
| 85 |
when using hardware tokens as part of multi-factor |
| 86 |
authentication and presenting the same prompt twice would |
| 87 |
confuse users. Use prompt=TokenCode (or some other |
| 88 |
relevant string different from Password) in this |
| 89 |
situation. |
| 90 |
|
| 91 |
force_prompt - Request a new password and not using the previously entered |
| 92 |
password. This useful for multi-factor authentication |
| 93 |
when used with a Token. |
| 94 |
|
| 95 |
max_challenge=# - configure maximum number of challenges that a server |
| 96 |
may request. This is a workaround for broken servers |
| 97 |
and disabled by default. |
| 98 |
|
| 99 |
prompt_attribute - Enable honoring of Prompt attribute sent from server for |
| 100 |
challenge-response to enable/disable of echoing of user |
| 101 |
input. Without this option all user input during |
| 102 |
challenge-response will be echoed. See RFC2869 Section 5.10 |
| 103 |
|
| 104 |
require_message_authenticator - Discard Access-Accept, Access-Challenge, and |
| 105 |
Access-Reject packets which do not contain Message-Authenticator. |
| 106 |
|
| 107 |
ipv4=no - Disable use of IPv4 |
| 108 |
|
| 109 |
ipv6=no - Disable use of IPv6 |
| 110 |
|
| 111 |
privilege_level - If set, the value of the Management-Privilege-Level RADIUS |
| 112 |
attribute from the Access-Accept response will be put in to |
| 113 |
the "Privilege" environment variable. |
| 114 |
|
| 115 |
--------------------------------------------------------------------------- |
| 116 |
|