mirror of
https://github.com/Yubico/yubico-pam.git
synced 2025-01-19 16:52:17 +01:00
Attempt to clarify format of mapping files
I didn't realise from the original version that it was a series of different token IDs - i thought it was different parts of the OTP. Hopefully this change clarifys whats really going on here. Part of the patch/doco for Issue 44. http://code.google.com/p/yubico-pam/issues/detail?id=44
This commit is contained in:
parent
bb91c37b05
commit
9377b14ef2
6
README
6
README
@ -246,8 +246,8 @@ each user you want to allow onto the system using a Yubikey.
|
||||
The mappings should look like this, one per line:
|
||||
|
||||
------
|
||||
<user name>:<Yubikey token ID>:<Yubikey token ID>:….
|
||||
<user name>:<Yubikey token ID>:<Yubikey token ID>:….
|
||||
<first user name>:<Yubikey token ID1>:<Yubikey token ID2>:….
|
||||
<second user name>:<Yubikey token ID3>:<Yubikey token ID4>:….
|
||||
------
|
||||
|
||||
Now add authfile=/etc/yubikey_mappings to your PAM configuration line, so it
|
||||
@ -265,7 +265,7 @@ directory and places the mapping in that file, the file must have only one
|
||||
line:
|
||||
|
||||
------
|
||||
<user name>:<Yubikey token ID>:<Yubikey token ID>
|
||||
<user name>:<Yubikey token ID1>:<Yubikey token ID2>
|
||||
------
|
||||
|
||||
This is much the same concept as the SSH authorized_keys file.
|
||||
|
Loading…
x
Reference in New Issue
Block a user