I am having a very unusual error on FDS version 1.0.3.
When we use ldapsearch to search for certain attributes we are getting
results back scrambled.
Upon further investigation we found that the 'scrambled' entries were
the intended entries just base64 encoded. Normally we'd expect the
results back in ascii of course.
The strange thing is that no matter how many times, and with any client
application, trying to fix the attribute results in no change.
Deleting the attribute will delete it, but when we re-add the attribute,
(checked for things like trailing spaces.), the entry will reappear as
the base64 entry (with a trailing space when translated back.)
It just appears 'stuck' and will not change to the intended text.
Any help or pointers on this would be appreciated.
When configuring sw that should authenticate ldap, they ask for ldap admin and
I wonder which is the difference between:
When shoud i use it ot the the other? who is "ldap admin"?
If you are interested in web services and how to expose LDAP data to
them, you will probably be interested in the DSML Gateway. We do not
have a binary distribution, but if you are familiar with Java, Ant, and
Tomcat, you should be able to build it.
See http://directory.fedoraproject.org/wiki/DSML_Gateway for more
Currently i'm using FDS 1.0.4 and wanted to migrate all data to new server running FDS 1.1. After
migrating the data it fully functional as otentication. But currently i'm having two FDS 1.1 machine
and wanted to do multimaster replicating.
When running the mmr.pl script i got the error message as shown below:
bash-3.2$ ./mmr.pl --host1 jstsvr3.jst.co.id --host2 sys03.jst.co.id --bindpw fdsmanager --host1_id
1 --host2_id 2 --bindpw fdsmanager --repmanpw repmanager --create
adding to jstsvr3.jst.co.id -> cn=changelog5,cn=config
failed to add changelog entry: failed to start changelog; error - 8 at ./mmr.pl line 253, <DATA>
Why this could happen? and what is the solution to solve this problem