Le 11/09/14 16:21, Lecko Mio a écrit : > Hi, > > I am using the ApacheDS library to create an LdapServer as kind of a proxy > which is accessed from different clients, i.e. it receives a request, adapt > sit if necessary and forwards it to another Ldap Server. For the received > requests the DNs given can have different formats, e.g. following some > example searches our proxy has to handle: > > ldapsearch -h xxx.xxx.xxx.xxx -p 389 -D uid=myadmin,ou=xxx -w yyyyy -b > p=33333333,o=corp,o=db objectclass=* > > ldapsearch -h xxx.xxx.xxx.xxx -p 389 -D 444444444 -w yyyyy -b > p=444444444,o=corp,o=db objectclass=* > > ldapsearch -h xxx.xxx.xxx.xxx -p 389 -D someUserName -w yyyyy -b > p=55555555,o=corp,o=db objectclass=* > > The first request/search is processed without a problem. A problem arises > only with the last two searches above where we get passed only a number or > a user name as the DN (without prefix and equal sign) -> so the > LdapProtocolDecoder seems to have a problem with the format. > > Thus the questions: is there a way to configure ApacheDs/my LdapServer in a > way that it also accepts "non-standard" DNs as above, e.g. '444444444'.
the -D parameter stands for BindDN. It must be a valid DN. You may want to use SASL to avoid the DN to be used (something lie -Q).
