pam: add realm_file option #3
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Using the realm_file option it is possible set the realm name on a per-user basis. The realm file must be located in the users home directory. An example setting would be realm_file=.linotp_realm
The realm_file parameter now understands the special tokens '~' (user home directory) and '%u' (username). '~~' can be used for a single tilde character. '%%' can be used for a single percent character. Unknown tokens (such as '%a') are copied verbatim. The realm file is no longer assumed to be in the users home directory. Use '~/.otp_token' instead.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Using the realm_file option it is possible to set the realm name on a per-user basis. An example setting would be
realm_file=~/.otp_realm
or
realm_file=/etc/linopt/%u.realm
We found ourselves in need of configuring different realms per account, and this was our solution, rather than prompting the user.