Version 0.4, when it starts, brings up "LDAP Error: No such object". (Version 0.3 did not)
but is displaying the LDAP entries OK.
AND (maybe related) when adding new entry, the Object class dropdown menu is empty.
We use RedHat OpenLDAP server, and realise we may have configuration issue with it - LDAP is new to us.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Version 0.4 tries to read the LDAP schema when it starts, and in your case it fails to read it.
The first thing to do is to verify that the user you are using has read access to the LDAP schema.
To do that try to connect to the LDAP server with an empty Root DN field.You should access to a list of properties. One of this properties is named "subschemaSubentry" and it's value is the dn of the directory schema.
You can then try to connect to the directory with a Root DN field equal to this value.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm experiencing the same thing. Honestly, I think it's my lack of understanding of OpenLDAP since an ldapsearch from my RedHat 9.0 command line acts pretty much the same way. If I specify -b "dc=domain,dc=com" on the ldapsearch field, I see my stuff but if I just wildcard the -b portion I get message 32 but as I understand it, I should get a dump of the entire directory. Maybe this has to do with RedHat's OpenLDAP default configuration?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Many problems have been solved using OpenLDAP since 0.4 release. These corrections will probably solve your problems at the same time but they will only be available in 0.5 release which is not ready yet.
Feel free to use the cvs latest version until the release goes out :o)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Version 0.4, when it starts, brings up "LDAP Error: No such object". (Version 0.3 did not)
but is displaying the LDAP entries OK.
AND (maybe related) when adding new entry, the Object class dropdown menu is empty.
We use RedHat OpenLDAP server, and realise we may have configuration issue with it - LDAP is new to us.
Version 0.4 tries to read the LDAP schema when it starts, and in your case it fails to read it.
The first thing to do is to verify that the user you are using has read access to the LDAP schema.
To do that try to connect to the LDAP server with an empty Root DN field.You should access to a list of properties. One of this properties is named "subschemaSubentry" and it's value is the dn of the directory schema.
You can then try to connect to the directory with a Root DN field equal to this value.
I'm experiencing the same thing. Honestly, I think it's my lack of understanding of OpenLDAP since an ldapsearch from my RedHat 9.0 command line acts pretty much the same way. If I specify -b "dc=domain,dc=com" on the ldapsearch field, I see my stuff but if I just wildcard the -b portion I get message 32 but as I understand it, I should get a dump of the entire directory. Maybe this has to do with RedHat's OpenLDAP default configuration?
Many problems have been solved using OpenLDAP since 0.4 release. These corrections will probably solve your problems at the same time but they will only be available in 0.5 release which is not ready yet.
Feel free to use the cvs latest version until the release goes out :o)