[ https://issues.apache.org/jira/brow...action_12475492 ]

Ersin Er commented on DIRSERVER-674:
------------------------------------

Well, I do not remember now the actual reason I proposed this for but I thin
k it does not hurt to add this feature. It just adds granularity.

> 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 ord
er to allow the service protocol type to be used in the Core. Protocol providers sho
uld be responsible for passing this "mandatory" parameter to JNDI while creating ini
tia
l contexts. This will allow finer grained administration based on the type o
f the service accessing to the core. For example, we may want to support Tri
ggers (or more refined features of Triggers) to apply only to LDAP operation
s, but not to Kerberos or N
TP 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.

[ Post a follow-up to this message ]