Hi,
I just fixed my problem but it seems not to be a common ldap problem but
a schema bootstrap one.
Even if my code is not made to be nice at this time, here is what work
for my test case (ie my client program had problem to search "OU=CA" and
now works fine)
$ diff BootstrapAttributeTypeRegistry.java
/cygdrive/d/tmp/BootstrapAttributeTypeRegistry.java
108,109c108,109
< id = oidRegistry.getOid( id );
<
---
> id = oidRegistry.getOid( id.toLowerCase() );//TBL
> //id = oidRegistry.getOid( id );
136a137,149
> //TBL start
> else if ( oidRegistry.hasOid( id.toLowerCase() ) )
> {
> try
> {
> return byOid.containsKey( oidRegistry.getOid(
id.toLowerCase() ) );
> }
> catch ( NamingException e )
> {
> return false;
> }
> }
> //TBL end
148a162,167
> //TBL start
> else if ( oidToSchema.containsKey( id.toLowerCase() ) )
> {
> return ( String ) oidToSchema.get( id.toLowerCase() );
> }
> //TBL end
The maps are not case insensitive...
Should I create a new issue or comment the DIRLDAP-35 ?
Cheers,
Tony
Alex Karasulu a écrit :
On Jul 2, 2005, at 5:57 PM, Emmanuel Lecharny wrote:
Sorry Tony, I think that there is already a JIRA entry for this :
http://issues.apache.org/jira/browse/DIRLDAP-35
Ditto I apologize for this as well Tony. I thought I had fixed this
a while back. Can you perhaps tack on the stack trace you get back
from the server so I can isolate the problem better?
Could you check if this is the same pb?
It probably is however there was another jira patch that jacob had
submitted to fix this issue. It was due to the schema registries not
looking up attributes in a case insensitive fashion. Perhaps this is
only one part of the problem. The stack trace Tony gets back will
help narrow it down even further and this should be pretty easy to fix.
BTW Tony are you working with the latest code from the Trunk or with
an older version of apacheds? If so this may be fixed in the trunk.
Sorry I don't remember off the top of my head if I applied Jacob's
patch.
Thanks for responding quickly Emmanuel.
Alex
On Sat, 2005-07-02 at 20:54 +0200, Tony Blanchard wrote:
I all,
I created a new entry like this ou=CA,ou=system and this is a pkiCA
object which I use with LDAPCertStore in JDK 1.5.
I have some openssl certificates which issuer DNs are "OU=CA,
OU=system"
The problem is that code like this does not work :
Context is already created with provider_url =
ldap://localhost:10389/ou=system
....
Attributes lAtts = MyOpenedLdapCtx.getAttributes ("OU=CA");
instead, this works:
Attributes lAtts = MyOpenedLdapCtx.getAttributes ("ou=CA");
Is there something I am missing or it is a bug I have to write in Jira
repository ?
I can not change the OU part of generated openssl certificate...
Thanks for help,
Tony Blanchard
---------------------------------------------------------------------
------------------
Wanadoo vous informe que cet e-mail a ete controle par l'anti-
virus mail.
Aucun virus connu a ce jour par nos services n'a ete detecte.
