directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <>
Subject [jira] Commented: (DIRSERVER-1413) Key pair generation attempts to add duplicate objectClass values
Date Thu, 01 Oct 2009 23:10:25 GMT


Emmanuel Lecharny commented on DIRSERVER-1413:

Oh, ok then.

last request from me ;) : did you saw this problem by just reading the code, or did you used
some portion of code which exhibited the misbehavior ?

Just asking because, if so, we would really appreciate to have this code be attached so that
we can :
- test the 1.5.5 server,
- have a unit test for us to debug the code 
- and last, not least, have this unit test part of our non-regression set of tests.

In any case, this seems to be a pretty simple correction, but I'm afraid that it can take
a bit of time to be done (I mean, a few days, maybe two weeks).

And, btw, if you feel like submitting a patch, that would be awesome !!!

Many thanks !

> Key pair generation attempts to add duplicate objectClass values
> ----------------------------------------------------------------
>                 Key: DIRSERVER-1413
>                 URL:
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.5.4
>            Reporter: Jeremy Gustie
>            Priority: Trivial
>   Original Estimate: 0.08h
>  Remaining Estimate: 0.08h
> The TlsKeyGenerator.addKeyPair(ServerEntry) method adds objectClass values for 'tlsKeyInfo'
and 'inetOrgPerson' without checking if they have already been added. This results in the
ERROR level message "The value 'inetOrgPerson' is incorrect, it hasn't been added" being emitted
from DefaultServerAttribute.add. In the case of the system administrator created by the DefaultDirectoryService,
this error message always appears on the first load as the 'inetOrgPerson' value is explicitly
added before calling addKeyPair. Replacing the objectClass.add(...) call with !objectClass.contains(...)/objectClass.add(...)
would prevent this error message from appearing.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message