directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kai Zheng (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DIRKRB-450) Allow to pass KdcOption related options from KinitTool down to KrbClient
Date Thu, 19 Nov 2015 00:18:10 GMT

    [ https://issues.apache.org/jira/browse/DIRKRB-450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15012442#comment-15012442
] 

Kai Zheng commented on DIRKRB-450:
----------------------------------

Ah, the codes and result look pretty good to me. Thanks Steve for getting this done!

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

Mime
View raw message