You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Kai Zheng (JIRA)" <ji...@apache.org> on 2015/11/07 02:34:11 UTC
[jira] [Commented] (DIRKRB-450) Add a method (or methods) to the
KrbClient.java that allows KdcOptions to be passed
[ https://issues.apache.org/jira/browse/DIRKRB-450?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14994851#comment-14994851 ]
Kai Zheng commented on DIRKRB-450:
----------------------------------
Hi Steve,
I thought KrbOptions may have already the needed option definitions. If necessary more can be added to it.
For admin related functionalities, we have another API *Kadmin*. Sure we can have further discussion, maybe in kerby ML?
> Add a method (or methods) to the KrbClient.java that allows KdcOptions to be passed
> -----------------------------------------------------------------------------------
>
> Key: DIRKRB-450
> URL: https://issues.apache.org/jira/browse/DIRKRB-450
> Project: Directory Kerberos
> Issue Type: Sub-task
> Reporter: 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)