You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Alex Karasulu (JIRA)" <di...@incubator.apache.org> on 2004/11/01 05:15:34 UTC

[jira] Closed: (DIREVE-67) alter owners of user entries under ou=users

     [ http://issues.apache.org/jira/browse/DIREVE-67?page=history ]
     
Alex Karasulu closed DIREVE-67:
-------------------------------

    Resolution: Fixed

Added changes to the operational attribute service interceptor to check the DN of the entry being added before setting the creatorsName.  If this DN is under the ou=users, ou=system context then the principal is set to the DN of the entry being added which is the new user.  This is done rather than taking the principal associated with the operation as the principal which would be the admin at uid=admin,ou=system.  Also note a test case was added and it passed with flying colors.

The changes were committed in revision 56195:

http://svn.apache.org/viewcvs.cgi?rev=56195&view=rev



> alter owners of user entries under ou=users
> -------------------------------------------
>
>          Key: DIREVE-67
>          URL: http://issues.apache.org/jira/browse/DIREVE-67
>      Project: Directory Eve
>         Type: Task
>   Components: interceptors, jndi-provider
>     Reporter: Alex Karasulu
>     Assignee: Alex Karasulu

>
> We want the user to own their own entry under ou=users.  This entails setting the creatorsName to the DN of the user entry, even though the entry is being created by the admin user.  This is the only way to do this and is a special rule within the operational attribute manager.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira