[jira] [Resolved] (DIRKRB-450) Allow to pass KdcOption related options from KinitTool down to KrbClient

["Jiajia Li (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/DIRKRB-450?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jiajia Li resolved DIRKRB-450.
------------------------------
       Resolution: Fixed
    Fix Version/s: 1.0.0-RC2

Thanks for Steve's work, I've committed.

commit 02e97e8ef8a833a6ef0a4a968de4353ede30b913
Author: plusplusjiajia <ji...@intel.com>
Date:   Thu Nov 19 09:54:16 2015 +0800

    DIRKRB-450 Allow to pass KdcOption related options from KinitTool down to KrbClient. Contributed by Steve.

> Allow to pass KdcOption related options from KinitTool down to KrbClient
> ------------------------------------------------------------------------
>
>                 Key: DIRKRB-450
>                 URL: https://issues.apache.org/jira/browse/DIRKRB-450
>             Project: Directory Kerberos
>          Issue Type: Sub-task
>            Reporter: Steve Moyer
>            Assignee: Steve Moyer
>             Fix For: 1.0.0-RC2
>
>         Attachments: kerby-mit-like-tgtrequest.png
>
>
> Currently, only KrbOptions can be set when making calls to the KrbClient.  At a minimum a method with a signature like the following would suffice:
>     public TgtTicket requestTgtWithOptions(KOptions requestOptions, KdcOptions kdcOptions);
> I'd be interested in having a more general discussion about the future direction of the Kerby client since we need the existing KrbClient functionality (which is KDC focused) as well as (remote) kpasswd and kadmin functionality.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)