directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Zheng, Kai" <kai.zh...@intel.com>
Subject [Kerberos] About the naming issue for the Kerberos project
Date Fri, 16 Jan 2015 08:07:09 GMT
Hi Pierre, Stefan, Lucas and other PMCs/committers,

Thanks for your accepting and supporting for the new Kerberos project. As you can see we’re
actively working on it and have some new contributors. We would proceed as soon as possible
according to the roadmap and plan discussed with you. Generally we’re towards a dedicated
Kerberos implementation, Kerberos is the base or foundation and the center concept, by which
we would support other authentication mechanisms as well via the well-defined Kerberos pre-authentication
framework, have our nice Directory Server as the default identity backend also leveraging
the powerful RBAC features as Pierre implied, and have the great management tool Directory
Studio in hand. With such support the new product may not be equally strong in security sense
as mature ones like MIT Kerberos do in its early phase, but should be good enough in management,
easiness and other aspects particularly in Java contexts. As the naming issue does block us
a lot, would you give your options to help resolve it the earlier the better, as Kiran suggested.
I’m sure “Apache Kerby” isn’t perfect but we would doubt there is ever such one. It’s
not a pet’s name as Kiran clarified, but does like a kid of Kerberos. Sure we could have
other even better names in future, but if we do we surely also can change to use it too, just
like currently I would give up the “Haox” naming even actually I’m not so happy in my
heart. Thanks!

Regards,
Kai

From: Zheng, Kai [mailto:kai.zheng@intel.com]
Sent: Wednesday, January 14, 2015 10:24 AM
To: Apache Directory Developers List
Subject: RE: [Kerberos] re-organizing the module structure

Appreciate if we could accelerate on this. It makes a lot sense to make the project comfortable
for all of us. Thanks!

Regards,
Kai

From: Kiran Ayyagari [mailto:kayyagari@apache.org]
Sent: Wednesday, January 14, 2015 9:18 AM
To: Apache Directory Developers List
Subject: Re: [Kerberos] re-organizing the module structure



On Wed, Jan 14, 2015 at 9:05 AM, Zheng, Kai <kai.zheng@intel.com<mailto:kai.zheng@intel.com>>
wrote:
Hi Kiran,

Thanks for taking care of this!

Looks like we could re-organize the project much better if we get the naming issue resolved
first. For example, if Kerby is used, maybe ‘kerby-asn1’ would be a choice, which allows
it to be used in other contexts/projects without worrying about polluting their global namespace.
yes, indeed, we all should come to a consensus on this naming issue
so I request all to cast their vote/opinion here https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-66

Just a quick reply. Will provide my thoughts for each item thoroughly late today.

Regards,
Kai

From: Kiran Ayyagari [mailto:kayyagari@apache.org<mailto:kayyagari@apache.org>]
Sent: Wednesday, January 14, 2015 8:11 AM
To: Apache Directory Developers List
Subject: [Kerberos] re-organizing the module structure

I suggest we reorganize the modules under directory-kerberos.

All the modules under 'contrib' are essential components hence must be
moved to the project root directory.

Add a new folder 'mech' or 'mechanisms' and move various auth mechanisms
like 'pkix', 'token' etc there.

Move 'haox-kdc/kdc-server' to the root level and the create a new folder
at the root level to hold all the backend implementations (and the ldap-identity-backend
will be moved here).

'contrib' folder can be used to store any contribution from other parties.

And, we should drop the project prefix from the folder names and set
that prefix in <artifactId> in the respective module's pom.xml.

For example, 'haox-asn1' should be renamed to 'asn1' and change the pom.xml
to contain <artifactId>haox-asn1</artifactId>
wdyt?
--
Kiran Ayyagari
http://keydap.com



--
Kiran Ayyagari
http://keydap.com
Mime
View raw message