directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Emmanuel Lecharny (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DIRSERVER-442) Synchronize suffix entries in configuration with entry on disk
Date Sun, 09 Mar 2014 07:54:46 GMT

     [ https://issues.apache.org/jira/browse/DIRSERVER-442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Emmanuel Lecharny updated DIRSERVER-442:
----------------------------------------

    Fix Version/s:     (was: 2.1.0)
                   2.0.0-M16

> Synchronize suffix entries in configuration with entry on disk
> --------------------------------------------------------------
>
>                 Key: DIRSERVER-442
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-442
>             Project: Directory ApacheDS
>          Issue Type: New Feature
>          Components: ldap
>            Reporter: Alex Karasulu
>            Assignee: Alex Karasulu
>            Priority: Minor
>             Fix For: 2.0.0-M16
>
>
> Stefan raised a good point in DIREVE-240 about changes to the suffix entry in the XML
configuration do not propagate (the entry is only used on startup).  Also changes to the entry
on disk via LDAP does not change the entry attributes in the XML configuration file.  
> First off we need to figure out if we are in fact going to change this behavoir.  If
we need to keep this data in synch or if the entry is only valid for the first startup.  
> Here are some of Stefan's comments:
> "This leads to the question, what the correct behaviour is, if someone changes the configuration
here (add some attributes, for example). The LDAP servers I know have the suffixes as a part
of the configuration, but adding a new suffix does not automatically add a corresponding entry.
This has to be done after server startup, manually."
> This issue is being created so we can close DIREVE-240 but not forget that some decision
must be made regarding this inconsistency.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Mime
View raw message