That is in fact my linked WIP branch, and I can confirm progress was stalled just to other priorities being set! It got to the point (in draft form) where authentication was working, but still need to work on extending IRoleManager.
I will say this, while I initially started using the Apache LDAP API, which is what’s present in that linked branch, I then started playing with UnboundID and Ldaptive (you can find that sandbox here: https://github.com/lqid/ldap-sandbox), which I found much easier to work with. Having said all that, I believe DataStax are in fact using the Apache LDAP API, so clearly it is robust enough… I’d love to start this back up to be honest, but business has priorities some very different things. However, this has been a good reminder that I should finish what I started, so thanks for that! ;) Feel free to reach out if you have any questions for me! Kindest regards, Daniel On 4 Mar 2017, 07:18 +1100, Sam Tunnicliffe <s...@beobal.com>, wrote: > This is something that has been discussed before and there's an JIRA open for > it already, it looks like progress has stalled but you might get some > pointers from the linked WIP branch. > > https://issues.apache.org/jira/browse/CASSANDRA-12294 > > > > On Fri, Mar 3, 2017 at 7:45 PM, Harika Vangapelli -T (hvangape - AKRAYA INC > > at Cisco) <hvang...@cisco.com> wrote: > > > I am trying to configure Cassnadra with LDAP , and I am trying to write > > > code and want to extend the functionality of > > > org.apache.cassandra.auth.PasswordAuthenticator and override authenticate > > > method but As PlainTextSaslAuthenticator innerclass has a private scope > > > not able to use method overriding. > > > > > > Please let us know what is the best way to implement LDAP security with > > > Apache Cassandra (or) a work around for this. > > > > > > Thanks, > > > Harika > > > > > > > > > Harika Vangapelli > > > Engineer - IT > > > hvang...@cisco.com > > > Tel: > > > Cisco Systems, Inc. > > > > > > > > > > > > United States > > > cisco.com > > > > > > Think before you print. > > > This email may contain confidential and privileged material for the sole > > > use of the intended recipient. Any review, use, distribution or > > > disclosure by others is strictly prohibited. If you are not the intended > > > recipient (or authorized to receive for the recipient), please contact > > > the sender by reply email and delete all copies of this message. > > > Please click here for Company Registration Information. > > > >
