I would definitely like to see a simple file-space approach to begin with and then would investigate the need for LDAP binding. For that, I would start by using a CLI approach to LDAP searching and binding and use that as the performance test case against JNDI.
Here are some references: http://www.openldap.org/ http://www.ietf.org/rfc/rfc2251.txt http://www.ietf.org/rfc/rfc2829.txt http://www.ietf.org/rfc/rfc2253.txt http://www.ietf.org/rfc/rfc1779.txt http://www.ietf.org/rfc/rfc2247.txt http://www.ietf.org/rfc/rfc1777.txt (v2) I will think about contributing but I need to shut down now for a move to a new building. I am happy to provide any advice I can, though, regardless. Robin. -----Original Message----- From: news [mailto:[email protected]] On Behalf Of Ted Zlatanov Sent: November 12, 2009 11:35 AM To: [email protected] Subject: Re: Cassandra access control On Thu, 12 Nov 2009 08:23:51 -0800 "Coe, Robin" <[email protected]> wrote: CR> I agree. Getting into LDAP will open a can of worms, especially if CR> the plan is to support Active Directory. There are a lot of RFCs on CR> the subject of LDAP and Active Directory doesn't support them all. CR> If LDAP is the plan, though, there needs to be support for ssl and CR> tls, at a minimum. Would you like to contribute or point me to a library that makes this easier? There's probably code in JAAS I can use, too, even if I'm not using the whole library. Anyhow, the simple file-based backend will come first and perhaps that's all we need. Ted
