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/03/17 00:03:39 UTC
[jira] [Commented] (DIRKRB-102) [Apache Kerby] A dedicated Kerberos
project
[ https://issues.apache.org/jira/browse/DIRKRB-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14364150#comment-14364150 ]
Kai Zheng commented on DIRKRB-102:
----------------------------------
To reflect the new project name *Apache Kerby*, the git repo was changed to:
https://git-wip-us.apache.org/repos/asf/directory-kerby.git
> [Apache Kerby] A dedicated Kerberos project
> --------------------------------------------
>
> Key: DIRKRB-102
> URL: https://issues.apache.org/jira/browse/DIRKRB-102
> Project: Directory Kerberos
> Issue Type: New Feature
> Reporter: Kai Zheng
> Labels: Kerberos
>
> As discussed in the community, we're going to create a dedicated Kerberos project based on Haox project codebase (https://github.com/drankye/haox) incorporating and consolidating the existing Kerberos functionalities in ApacheDS. The long term goal is to establish a first class Kerberos implementation in Java for the Apache world targeting today's environments in cloud, Hadoop and mobile. It will provides rich, intuitive and interoperable library and facilities that integrate multiple authentication mechanisms including PKI, OTP and token (OAuth) as desired in above mentioned modern environments.It will also implement a KDC server that can integrate various identity back ends including simple memory database, SQL database and LDAP server by dynamic plugin and loading approach, which allows it to be utilized in various contexts and scenarios.
> This serves as the master JIRA to track all the related tasks for the new sub project. With the fundamental aspects and tasks resolved, we would go to next phase targeting an Apache TLP project, as we agreed in the discussion.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
RE: [jira] [Commented] (DIRKRB-102) [Apache Kerby] A dedicated
Kerberos project
Posted by "Zheng, Kai" <ka...@intel.com>.
Hi all,
Please aware this change.
To reflect the new project name *Apache Kerby*, the git repo was changed to:
https://git-wip-us.apache.org/repos/asf/directory-kerby.git
Regards,
Kai
-----Original Message-----
From: Kai Zheng (JIRA) [mailto:jira@apache.org]
Sent: Tuesday, March 17, 2015 7:04 AM
To: dev@directory.apache.org
Subject: [jira] [Commented] (DIRKRB-102) [Apache Kerby] A dedicated Kerberos project
[ https://issues.apache.org/jira/browse/DIRKRB-102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14364150#comment-14364150 ]
Kai Zheng commented on DIRKRB-102:
----------------------------------
To reflect the new project name *Apache Kerby*, the git repo was changed to:
https://git-wip-us.apache.org/repos/asf/directory-kerby.git
> [Apache Kerby] A dedicated Kerberos project
> --------------------------------------------
>
> Key: DIRKRB-102
> URL: https://issues.apache.org/jira/browse/DIRKRB-102
> Project: Directory Kerberos
> Issue Type: New Feature
> Reporter: Kai Zheng
> Labels: Kerberos
>
> As discussed in the community, we're going to create a dedicated Kerberos project based on Haox project codebase (https://github.com/drankye/haox) incorporating and consolidating the existing Kerberos functionalities in ApacheDS. The long term goal is to establish a first class Kerberos implementation in Java for the Apache world targeting today's environments in cloud, Hadoop and mobile. It will provides rich, intuitive and interoperable library and facilities that integrate multiple authentication mechanisms including PKI, OTP and token (OAuth) as desired in above mentioned modern environments.It will also implement a KDC server that can integrate various identity back ends including simple memory database, SQL database and LDAP server by dynamic plugin and loading approach, which allows it to be utilized in various contexts and scenarios.
> This serves as the master JIRA to track all the related tasks for the new sub project. With the fundamental aspects and tasks resolved, we would go to next phase targeting an Apache TLP project, as we agreed in the discussion.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)