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/06/11 11:47:00 UTC

[jira] [Updated] (DIRKRB-131) Update the Kerberos part in Directory Server in favor of Kerby

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

Kai Zheng updated DIRKRB-131:
-----------------------------
    Fix Version/s: 2.0.0-RC1

> Update the Kerberos part in Directory Server in favor of Kerby
> --------------------------------------------------------------
>
>                 Key: DIRKRB-131
>                 URL: https://issues.apache.org/jira/browse/DIRKRB-131
>             Project: Directory Kerberos
>          Issue Type: Sub-task
>            Reporter: Kai Zheng
>             Fix For: 2.0.0-RC1
>
>
> As discussed in the mailing list, we would decouple Kerberos logics from the Directory Server, to better maintain the dependencies and avoid the complexities. In the end, the Directory Server can be used as an identity backend for the KDC server in the plugin or dynamical loading approach.
> 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)