All-

I need some pointers to doc and/or advice on how to deal with a custom
LDAP schema.  My DirectoryServer instance is proxying requests to a custom
LDAP server with a custom schema, and then processing the responses and
passing them back to the client.  However, the end client wants to submit
to my proxy server a search filter that contains a custom attribute in the
backend server.  When the client submits this filter to Apache DS, the
NormalizationService intercepts it before the request reaches my
DirectoryPartition implementation, and----failing to find it in its own
schemas---returns an empty enumeration.

Clearly, I need to either a.) load the custom schema or b.) modify the
NormalizationSchema not to perform the local attribute check.  I'd prefer
the former (since that seems less hack-y), but I have no idea how to go
about it or what kind of pain I'm in for.

Any advice appreciated.

Regards,

Martin Zaidel

[ Post a follow-up to this message ]

MartinZaidel-1I9K1FznhJHvnOemgxGiVw@public.gmane.org wrote:
>
> All-
>
> I need some pointers to doc and/or advice on how to deal with a custom
> LDAP schema.
http://www.archivum.info/dev-aYN4UC...1/msg00051.html

http://directory.apache.org/subproj...ers/plugin.html

Unfortunately all this is old maven 1 build process stuff.  But you may
be using that for your build.  If you want a good example project of how
this is done with the maven2 plugin take a look at this simple example
project here:

https://svn.safehaus.org/repos/sand...econ-m2/schema/

HTH,
Alex

[ Post a follow-up to this message ]

I have a patch I use to discover a proxy LDAP server's schema and
register it with ApacheDS dynamically when the proxy partition starts
up.

If you're interested I can pass it on, but recently something seems to
have changed with GlobalRegistries/SchemaService which caused a
problem I haven't had time to fully diagnose. I can perhaps look into
the problem next week if anyone is interested in the patch (I can't
even remember exactly what it was now) .

Note that ultimately my feeling is that ApacheDS will need some
specialised support for proxy partitions, as ideally they require a
much more "hands-off" approach from the server (there is no need to
normalise/schema check etc etc if the remote LDAP server is going to
do it all again anyway). Even then contributing the remote schema
dynamically may still have some value.

[ Post a follow-up to this message ]

Norbet Reilly wrote:
> I have a patch I use to discover a proxy LDAP server's schema and
> register it with ApacheDS dynamically when the proxy partition starts
> up.
>
> If you're interested I can pass it on, but recently something seems to
> have changed with GlobalRegistries/SchemaService which caused a
> problem I haven't had time to fully diagnose. I can perhaps look into
> the problem next week if anyone is interested in the patch (I can't
> even remember exactly what it was now) .
>
> Note that ultimately my feeling is that ApacheDS will need some
> specialised support for proxy partitions, as ideally they require a
> much more "hands-off" approach from the server (there is no need to
>
You do know that you can remove interceptors stripping away the
functionality by editing the server.xml file?

Alex

[ Post a follow-up to this message ]

Sure, that's what I'm doing currently (I remove all the services
except for authentication). However as normalisation is used
internally even when the normalisation service isn't active, the
schema problem has to be solved anyway.

However, ultimately I could imagine a single AD instance supporting
both proxy partitions and a JDBM partition which tends to suggest the
interceptor chain may ultimately need to be associated with the
partition rather then the root nexus.

[ Post a follow-up to this message ]