Dear all,
I like to downgrade the ldap communication protocol to do some experiments. An api which has been designed in 2005 can not work with my ldap server ( suse 11.1) as the log reports
````````````````````````` historical protocol version requested, use LDAPv3 instead
`````````````````````````````````````
so i need to temporarily allow the old v2 protocol so that the api can communicate with the ldap server. How can i do this ?
Thanks
ok, find it
`````````````````` allow bind_v2 ````````````````````````
J. Bakshi wrote:
Dear all,
I like to downgrade the ldap communication protocol to do some experiments. An api which has been designed in 2005 can not work with my ldap server ( suse 11.1) as the log reports
historical protocol version requested, use LDAPv3 insteadso i need to temporarily allow the old v2 protocol so that the api can communicate with the ldap server. How can i do this ?
Thanks
J. Bakshi wrote:
ok, find it
allow bind_v2
I'm not sure whether you are aware of the issues you might have with that. E.g. your old application or API might expect another character set to be used with LDAPv2, e.g. T.61. The use of UTF-8-encoded Unicode for DirectoryString syntax was specified in LDAPv3.
If you write a new application with that API you should rather find out how to use LDAPv3 with that API.
Ciao, Michael.
Michael Ströder wrote:
J. Bakshi wrote:
ok, find it
allow bind_v2I'm not sure whether you are aware of the issues you might have with that. E.g. your old application or API might expect another character set to be used with LDAPv2, e.g. T.61. The use of UTF-8-encoded Unicode for DirectoryString syntax was specified in LDAPv3.
If you write a new application with that API you should rather find out how to use LDAPv3 with that API.
Ciao, Michael.
Hello,
Thanks for sharing the information. I was really not aware about it. The API I am using for my experiment is a year-2005 build API hence an old one. I am using this api just to authenticate the users stored in ldap server. I have already communicated with the author of the API so that I can modify it to use with LDAPv3
Thanks a lot....
Michael Ströder wrote:
J. Bakshi wrote:
The API I am using for my experiment is a year-2005 build API hence an old one.
Why do you use it? I'd recommend to rethink that...
Ciao, Michael.
I have already sent an email to the author and wanted to know how to modify it so that it can communicate with LDAPv3 too.
Thanks
J. Bakshi wrote:
Dear all,
I like to downgrade the ldap communication protocol to do some experiments. An api which has been designed in 2005 can not work with my ldap server ( suse 11.1) as the log reports
historical protocol version requested, use LDAPv3 insteadso i need to temporarily allow the old v2 protocol so that the api can communicate with the ldap server. How can i do this ?
Add this line in slapd.conf (LDAP v3 is still supported after you add this) and restart openldap:
---- allow bind_v2 ----
openldap-technical@openldap.org
-
J. Bakshi -
Michael Ströder -
Zhang Huangbin