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/07/02 00:25:04 UTC

[jira] [Resolved] (DIRKRB-315) Consistent checking for KDC network transport settings

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

Kai Zheng resolved DIRKRB-315.
------------------------------
    Resolution: Fixed

commit bb6cce191204a7d7acdc95aa37ef0e5877ece5fc
Author: drankye <ka...@intel.com>
Date:   Thu Jul 2 06:23:23 2015 +0800

    Network transport related improvements, addressing DIRKRB-313, 314, and 315

> Consistent checking for KDC network transport settings
> ------------------------------------------------------
>
>                 Key: DIRKRB-315
>                 URL: https://issues.apache.org/jira/browse/DIRKRB-315
>             Project: Directory Kerberos
>          Issue Type: Improvement
>            Reporter: Kai Zheng
>            Assignee: Kai Zheng
>
> In KDC side, for network transport and ports, we allow to configure them via configuration file, and also allow to set startup options directly via the API. This is to perform some consistent checking like suggested in client side. For example, if {{allowTcp}} is true, then {{kdcTcpPort}} should be correctly equipped.



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