Continuation of evaluation of ApacheDS as part of a preemptive cache

[Tom Bruser <ml...@tombruser.com>]

I've been making some progress in standing up a memory partition for
ApacheDS and still have some ways to go to make a custom partition to store
the data as I see better fit for my purposes.

My preemptive cache will be available to *most* of our clients via a simple
restful service call.  The purpose of looking at ApacheDS is to deal with
one client that is set up to only talk to LDAP.  This client will
essentially connect in to LDAP and perform a simple search.  Think in terms
of an out of the box CMS that needs to import its users and groups
information.

Just to make sure I'm not trying to over-architect the solution, is there a
better way to provide a facility to let an LDAP client bind (log in),
interpret or parse the LDAP query (filter) into something that can query
against simple collections of POJOs, and return an LDAP-friendly response?
This is based on my current direction to stand up ApacheDS and customize a
memory partition so that it can map to my POJOs.  It just seems so far that,
albeit possibly due to ignorance, am trying too hard to structure my
in-memory data to cater to how ApacheDS would like to see it represented as
opposed to just trying to figure out what the client is asking for and find
it within the structure that I'm already planning to use for the other 90%
of clients.  I've seen some mention of FilterParser, but did not yet find
much information on how to use it... of course, I'd still need a means to
accept the filter from the client to begin with even once I learn how to use
it.

Re: Continuation of evaluation of ApacheDS as part of a preemptive cache

[Kiran Ayyagari <ka...@apache.org>]

On Mon, Mar 11, 2013 at 10:38 PM, Tom Bruser <ml...@tombruser.com> wrote:

> I've been making some progress in standing up a memory partition for
> ApacheDS and still have some ways to go to make a custom partition to store
> the data as I see better fit for my purposes.
>
> My preemptive cache will be available to *most* of our clients via a simple
> restful service call.  The purpose of looking at ApacheDS is to deal with
> one client that is set up to only talk to LDAP.  This client will
> essentially connect in to LDAP and perform a simple search.  Think in terms
> of an out of the box CMS that needs to import its users and groups
> information.
>
> Just to make sure I'm not trying to over-architect the solution, is there a
> better way to provide a facility to let an LDAP client bind (log in),
> interpret or parse the LDAP query (filter) into something that can query
> against simple collections of POJOs, and return an LDAP-friendly response?
> This is based on my current direction to stand up ApacheDS and customize a
> memory partition so that it can map to my POJOs.  It just seems so far
> that,
> albeit possibly due to ignorance, am trying too hard to structure my
> in-memory data to cater to how ApacheDS would like to see it represented as
> opposed to just trying to figure out what the client is asking for and find
> it within the structure that I'm already planning to use for the other 90%
> of clients.  I've seen some mention of FilterParser, but did not yet find
> much information on how to use it... of course, I'd still need a means to
> accept the filter from the client to begin with even once I learn how to
> use
> it.
>
> the best way is to override the search( SearchOperationContext
searchContext ) method
in your custom partition, The parsed filter is available as a java object
(ExprNode) saving your
time from parsing from there you are on your own with your logic :)

Please post here if in case you encounter any hurdles while trying to
achieving what you need.


-- 
Kiran Ayyagari
http://keydap.com