[
https://issues.apache.org/jira/browse/DIRSERVER-676?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481478
]
Alex Karasulu commented on DIRSERVER-676:
-----------------------------------------
Ersin I still need to know if you need this right away. You waiting on it for
something to go into 1.5.0?
Also it might be better to have a signature like so instead:
( ServerLdapContext ) ( ( ServerLdapContext ) invocation.getCaller()
).getRootContextFor( env );
Where env is a map/hash of JNDI properties that are used to determine the
mechanism, principal
and credentials with which to get the context for that user.
If the calling method has access to this information (when as admin for
example) or executing
in code that has access to the entry of the user it should be easy to
authenticate and create a
context for the requested user.
How does this sound?
> Provide a method for gathering a handle on root DSE on behalf of any principal
> ------------------------------------------------------------------------------
>
> Key: DIRSERVER-676
> URL: https://issues.apache.org/jira/browse/DIRSERVER-676
> Project: Directory ApacheDS
> Issue Type: New Feature
> Components: core
> Reporter: Ersin Er
> Assigned To: Alex Karasulu
> Fix For: 1.5.0
>
>
> We are currently able to get a handle on root DSE for the active principal
> invoking the operation. Here is a code snippet for that:
> ( ServerLdapContext ) ( ( ServerLdapContext ) invocation.getCaller()
> ).getRootContext();
> However we need to get handle on root DSE for any principal also; maybe
> something like this:
> ( ServerLdapContext ) ( ( ServerLdapContext ) invocation.getCaller()
> ).getRootContextFor( userDn );
> This will allow us to run Triggers with creators' credentials.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
