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/04/21 14:33:59 UTC
[jira] [Updated] (DIRKRB-132) Decouple Kerberos from the Directory
Studio
[ https://issues.apache.org/jira/browse/DIRKRB-132?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Kai Zheng updated DIRKRB-132:
-----------------------------
Description:
As discussed in the mailing list, we would decouple Kerberos logics from the Directory related projects and codes, to better maintain the dependencies and avoid the complexities. The Directory Studio should be also taken care of, but I'm not sure we would totally remove the embedded KDC server from the tool itself since that involves compatibility concern. Please give your feedback here, thanks.
Updated and re-purposed, according to [~akiran]'s email:
{quote}
that feature will remain there, later will be swapped with Kerby's core when it is ready, but the
Kerberos feature of ApacheDS stays.
In the end we have two:
1. Embedded Kerby in ApacheDS
2. Standalone Kerby
{quote}
was:As discussed in the mailing list, we would decouple Kerberos logics from the Directory related projects and codes, to better maintain the dependencies and avoid the complexities. The Directory Studio should be also taken care of, but I'm not sure we would totally remove the embedded KDC server from the tool itself since that involves compatibility concern. Please give your feedback here, thanks.
> Decouple Kerberos from the Directory Studio
> -------------------------------------------
>
> Key: DIRKRB-132
> URL: https://issues.apache.org/jira/browse/DIRKRB-132
> Project: Directory Kerberos
> Issue Type: Sub-task
> Reporter: Kai Zheng
>
> As discussed in the mailing list, we would decouple Kerberos logics from the Directory related projects and codes, to better maintain the dependencies and avoid the complexities. The Directory Studio should be also taken care of, but I'm not sure we would totally remove the embedded KDC server from the tool itself since that involves compatibility concern. Please give your feedback here, thanks.
> Updated and re-purposed, according to [~akiran]'s email:
> {quote}
> that feature will remain there, later will be swapped with Kerby's core when it is ready, but the
> Kerberos feature of ApacheDS stays.
> In the end we have two:
> 1. Embedded Kerby in ApacheDS
> 2. Standalone Kerby
> {quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)