The module is for authentication of YubiKeys, either with online validation of OTP, or offline validation with HMAC-SHA1 challenge-response.
- Turns on debugging to STDOUT
- Set the mode of operation, client for OTP validation and challenge-response for challenge-response validation, client is the default.
- Set the location of the file that holds the mappings of Yubikey token IDs to user names. The format is username:first_public_id:second_public_id:... default location of the file is $HOME/.yubico/authorized_yubikeys.
- Set to your client identity.
- Set to your client key in base64 format. The client key is also known as API key, and provides integrity in the communication between the client (you) and the validation server. If you want to get one for use with the default YubiCloud service, please go to https://upgrade.yubico.com/getapikey/
- Set to enable all authentication attempts to succeed (aka presentation mode).
- Before prompting the user for their password, the module first tries the previous stacked module´s password in case that satisfies this module as well.
- The argument use_first_pass forces the module to use a previous stacked modules password and will never prompt the user - if no password is available or the password is not appropriate, the user will be denied access.
- List of URL templates to be used. This is set by calling ykclient_set_url_bases. The list should be in the format: https://api1.example.com/wsapi/2.0/verify;https://api2.example.com/wsapi/2.0/verify
- This option should not be used, please use the urllist option instead. Set the URL template to use, this is set by calling ykclient_set_url_template. The URL should be set in the format https://api.example.com/wsapi/2.0/verify?id=%d&otp=%s
- Specify the path where X509 certificates are stored. This is required if https or ldaps are used in url and ldap_uri respectively.
- This argument is used to show the OTP (One Time Password) when it is entered, i.e. to enable terminal echo of entered characters. You are advised to not use this, if you are using two factor authentication because that will display your password on the screen. This requires the service using the PAM module to display custom fields. For example, OpenSSH requires you to configure "ChallengeResponseAuthentication no".
- Specify the LDAP server URI (e.g. ldap://localhost).
- Specify the LDAP server host (default LDAP port is used). Deprecated. Use ldap_uri instead.
- The dn where the users are stored (eg: ou=users,dc=domain,dc=com). If ldap_filter is used this is the base from which the subtree search will be performed.
- The LDAP attribute used to store user names (eg:cn).
- The LDAP attribute used to store the Yubikey id.
- The prefix of the LDAP attribute's value, in case of a generic attribute, used to store several types of ids.
- Length of ID prefixing the OTP (this is 12 if using the YubiCloud).
- The user to attempt a LDAP bind as.
- The password to use on LDAP bind.
- An ldap filter to use for attempting to find the correct object in LDAP. In this string %u will be replaced with the username.
- Ca certfile for the LDAP connection.
- Path of a system wide directory where challenge response files can be found for users. Default location is $HOME/.yubico/
auth sufficient pam_yubico.so id=16 debug
auth required pam_yubico.so mode=challenge-response
auth required pam_yubico.so id=16 ldap_uri=ldaps://ldap.example.com ldap_filter=(uid=%u) yubi_attr=yubiKeyId
- If authfile is not set this file is used for the mapping between YubiKey public id and in client mode.
- If chalresp_path is not set these files are used to hold next challenge and expected response for the user in challenge-response mode. If chalresp_path is set the filename will be username instead of challenge.
Report yubico-pam bugs in the issue tracker: https://github.com/Yubico/yubico-pam/issues