It seems the apacheds database does not like "é" chars.
I even think trying to destroy such entries containing such chars lead to database severe corruption but I have no real and systematic clue yet.
To reproduce, simply try to put a group with a "é" char in the cn attribute with JXplorer. Now, try to modify it. Exception araise.
Now, in my client code, I see SearchResult returned with bad results in getName() or getNameInNameSpace(). It seems it returns a string with " " replaced by "%20" and "é" char replaced with a value like /ufffd or something like this.
Nevertheless, if I retrieve the attributes from the SearchResult I get the correct "cn" value with a correct "é" char in it
Description
It seems the apacheds database does not like "é" chars.
I even think trying to destroy such entries containing such chars lead to database severe corruption but I have no real and systematic clue yet.
To reproduce, simply try to put a group with a "é" char in the cn attribute with JXplorer. Now, try to modify it. Exception araise.
Now, in my client code, I see SearchResult returned with bad results in getName() or getNameInNameSpace(). It seems it returns a string with " " replaced by "%20" and "é" char replaced with a value like /ufffd or something like this.
Nevertheless, if I retrieve the attributes from the SearchResult I get the correct "cn" value with a correct "é" char in it
Bug
Closed
Major
Putting some chars like "é" in common name with JXPlorer or my client code creates problems
