[
https://issues.apache.org/jira/browse/DIRSERVER-674?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482570
]
Emmanuel Lecharny commented on DIRSERVER-674:
---------------------------------------------
Ersin, can we postpone this issue to 1.5.1 ? Is it really necessary to have
this parameter ? What about including this request into a vast refactoring of
the JNDI usage inside the server for a 2.0 version of the server ?
> Support for directory.service.type as a JNDI parameter
> ------------------------------------------------------
>
> Key: DIRSERVER-674
> URL: https://issues.apache.org/jira/browse/DIRSERVER-674
> Project: Directory ApacheDS
> Issue Type: New Feature
> Components: changepw, core, dhcp, dns, kerberos, ldap, ntp
> Reporter: Ersin Er
> Priority: Minor
> Fix For: 1.5.0
>
>
> An environment parameter named directory.service.type may be passed to JNDI
> in order to allow the service protocol type to be used in the Core. Protocol
> providers should be responsible for passing this "mandatory" parameter to
> JNDI while creating initial contexts. This will allow finer grained
> administration based on the type of the service accessing to the core. For
> example, we may want to support Triggers (or more refined features of
> Triggers) to apply only to LDAP operations, but not to Kerberos or NTP
> operations. This is not only an improvement for Triggers but for the
> core-services interaction as a whole.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
