Support for directory.service.type as a JNDI parameter
------------------------------------------------------

Key: DIRSERVER-674
URL: http://issues.apache.org/jira/browse/DIRSERVER-674
Project: Directory ApacheDS
Issue Type: New Feature
Components: changepw, core, dhcp, dns, kerberos, ldap, ntp
Affects Versions: 1.1.0
Reporter: Ersin Er
Priority: Minor
Fix For: 1.1.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 J
NDI 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 Trigg
ers (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-se
rvices interaction as a whole.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://iss
ues.apache.org/ji...nistrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[ Post a follow-up to this message ]