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

["Kai Zheng (JIRA)" <ji...@apache.org>]

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

Kai Zheng updated DIRKRB-450:
-----------------------------
    Summary: Allow to pass KdcOption related options from KinitTool down to KrbClient  (was: Allow to set and pass KdcOption related options from KinitTool down to KrbClient)

> 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
>
> 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)