[SSSD] [PATCHES] krb5: new option krb5_map_user

Jakub Hrozek jhrozek at redhat.com
Thu May 28 09:29:17 UTC 2015


On Thu, May 28, 2015 at 11:09:50AM +0200, Pavel Reichl wrote:
> 
> 
> On 05/28/2015 11:04 AM, Jakub Hrozek wrote:
> >On Wed, May 27, 2015 at 09:40:13AM +0200, Jakub Hrozek wrote:
> >>On Tue, May 26, 2015 at 04:36:18PM +0200, Pavel Reichl wrote:
> >>> From 923e68ba56f276db473a38fffe339a0dc9770a4f Mon Sep 17 00:00:00 2001
> >>>From: Pavel Reichl <preichl at redhat.com>
> >>>Date: Thu, 30 Apr 2015 06:43:05 -0400
> >>>Subject: [PATCH] krb5: new option krb5_map_user
> >>>
> >>>New option `krb5_map_user` providing mapping of ID provider names to
> >>>Kerberos principals.
> >>>
> >>>Resolves:
> >>>https://fedorahosted.org/sssd/ticket/2509
> >>[...]
> >>
> >>>+                             <quote>joe</quote> and <quote>dick</quote> are
> >>>+                             UNIX user names and <quote>juser</quote> and
> >>>+                             <quote>richard</quote> are primaries of kerberos
> >>>+                             principals. For user <quote>joe</quote> resp.
> >>>+                             <quote>dick</quote> SSSD will try to kinit as
> >>>+                             <quote>dick at REALM</quote> resp.
> >>                                 kinit as juser at REALM right?
> >>
> >>>+                             <quote>richard at REALM</quote>.
> >>>+                        </para>
> >>>+
> >>>+                        <para>
> >>>+                            Default: not set
> >>>+                        </para>
> >>>+                    </listitem>
> >>>+                </varlistentry>
> >>>+
> >>>              </variablelist>
> >>>          </para>
> >>>      </refsect1>
> >>But since this is the last nitpick I found (for real this time :-)) I
> >>can fix this up locally and push..
> >Attached is a patch I'm about to push.
> >
> Man page looks good to me. Sorry for so many mistakes in such a short text.

CI link: http://sssd-ci.duckdns.org/logs/job/16/06/summary.html
* master: aa8a8318aaa3270e9d9957d0c22dec6342360a37
* sssd-1-12: c494e100f9b2422e2890507f63019afcaff9b7c6

I still think it makes sense to push the patch to sssd-1-12 as well --
it's not too risky and there's quite a few users who'd like to see this
feature.



More information about the sssd-devel mailing list