| Key: |
DIRSERVER-674
|
| Type: |
New Feature
|
| Status: |
Closed
|
| Resolution: |
Invalid
|
| Priority: |
Minor
|
| Assignee: |
Unassigned
|
| Reporter: |
Ersin Er
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
| Resolution Date: |
19/Jun/08 02:51 AM
|
|
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.
|
|
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. |
Show » |
| No work has yet been logged on this issue.
|
|
Support for directory.service.type as a JNDI parameter
