Support for directory.service.type as a JNDI parameter

• Key: DIRSERVER-674
• Type: New Feature
• Status: Closed
• Resolution: Invalid
• Priority: Minor
• Assignee: Unassigned
• Reporter: Ersin Er
• Component/s: changepw, core, dhcp, dns, ldap, ntp
• Fix Version/s: 1.5.3

Description

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.

Comments

[Alex Karasulu]

I don't know what the value of this is can you elaborate some more. Why would a trigger not apply in both cases when operations occur externally or by way of services in ApacheDS? Don't we want both of them to operate the same?

[Ersin Er]

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

[Emmanuel Lecharny]

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 ?

[Ersin Er]

Postponing to 1.5.1.

[Alex Karasulu]

Delaying this yet again.

Postponed again.

[Alex Karasulu]

will completely chage SP stuff soon making this unnecessary