[ 
https://issues.apache.org/jira/browse/DIRSERVER-1413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12761660#action_12761660
 ] 

Jeremy Gustie edited comment on DIRSERVER-1413 at 10/2/09 11:32 AM:
--------------------------------------------------------------------

A "contains" check was added to the DefaultServerAttribute.add() which does 
solve this issue in 1.5.5. Note that to reproduce the issue in 1.5.4 I needed 
to start a default directory service with no partitions (aside from the system 
partition) and an empty working directory. Looks like an upgrade to 1.5.5 was 
all that was needed, sorry!

      was (Author: jgustie):
    A "contains" check was added to the DefaultServerAttribute.add() which does 
solve this issue in 1.5.5. Note that to reproduce the issue in 1.5.4 I needed 
to start a default directory service with no partitions (aside from the system 
partition) and an empty working directory.
  
> Key pair generation attempts to add duplicate objectClass values
> ----------------------------------------------------------------
>
>                 Key: DIRSERVER-1413
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1413
>             Project: Directory ApacheDS
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.5.4
>            Reporter: Jeremy Gustie
>            Priority: Trivial
>             Fix For: 1.5.5
>
>   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.

Reply via email to