Username mappings #6
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
|
Apologies for the long delay in giving you feedback on this. This looks like a reasonable thing to support to me, but I'd definitely want a good test suite to go with it before merging. I would probably eventually write that myself, but writing tests, as for |
Add support for writing regex based username -> principal mappings.
JKDingwall
force-pushed
the
username-mappings
branch
from
df76115 to
db80467
Compare
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.
reference: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=860244
This branch adds a new configuration option to the appdefaults [pam] settings in krb5.conf called "mappings". This allows user names to be mapped to kerberos principals using regex rules and is comparable to the option by the same name available in the RHEL pam_krb5 implementation. This solves a problems for us where Samba's winbind does not work across one-way domain trusts but we wanted to allow REMOTEDOMAIN\user style user names.
At this point the test code is inline and there are no separate test cases so perhaps as it stands the branch could be considered a request for comment.