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/10/31 06:41:32 UTC

[jira] Created: (DIREVE-68) Authorization Service: hardcode simple authorization rules for safty

Authorization Service: hardcode simple authorization rules for safty
--------------------------------------------------------------------

         Key: DIREVE-68
         URL: http://issues.apache.org/jira/browse/DIREVE-68
     Project: Directory Eve
        Type: Task
  Components: interceptors  
    Reporter: Alex Karasulu
 Assigned to: Alex Karasulu 


We need to prevent everyone except the admin user from accessing the admin user's entry.  It should not be returned on searches and lookup's should fail if these operations are not being conducted by the admin.  This will prevent other users from being able to read the admin's entry or alter it.  In general I'm not in favor of hard coding rules but this is one that is almost universally valid and is ok to hardcode.  After all this can be changed later as dynamic authorization policy mechanisms are put into place.  Also modifyRdn and delete operations will not be allowed!

Furthermore we can extend this to regular users where only those that own their entry under ou=users,ou=system can read, or modify their entry.  No modifyRdn, or delete operations are allowed on these entries by any user except the admin user.  The admin user can do anything it wants to do.  Other users besides the creator/owner cannot read the userPassword field.

This is basically a new interceptor implementation.


-- 
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


[jira] Commented: (DIREVE-68) Authorization Service: hardcode simple authorization rules for safty

Posted by "Alex Karasulu (JIRA)" <di...@incubator.apache.org>.
     [ http://nagoya.apache.org/jira/browse/DIREVE-68?page=comments#action_54869 ]
     
Alex Karasulu commented on DIREVE-68:
-------------------------------------

Added protection against changes and deletes in the following revision:

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

We still need to have a policy for dealing with search, list and lookup.  I'm thinking the best approach is to not return anything at all for anyone except the admin user.  Other users besides the admin should not even know about the existance of these user accounts.

> Authorization Service: hardcode simple authorization rules for safty
> --------------------------------------------------------------------
>
>          Key: DIREVE-68
>          URL: http://nagoya.apache.org/jira/browse/DIREVE-68
>      Project: Directory Eve
>         Type: Task
>   Components: interceptors
>     Reporter: Alex Karasulu
>     Assignee: Alex Karasulu

>
> We need to prevent everyone except the admin user from accessing the admin user's entry.  It should not be returned on searches and lookup's should fail if these operations are not being conducted by the admin.  This will prevent other users from being able to read the admin's entry or alter it.  In general I'm not in favor of hard coding rules but this is one that is almost universally valid and is ok to hardcode.  After all this can be changed later as dynamic authorization policy mechanisms are put into place.  Also modifyRdn and delete operations will not be allowed!
> Furthermore we can extend this to regular users where only those that own their entry under ou=users,ou=system can read, or modify their entry.  No modifyRdn, or delete operations are allowed on these entries by any user except the admin user.  The admin user can do anything it wants to do.  Other users besides the creator/owner cannot read the userPassword field.
> This is basically a new interceptor implementation.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.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


[jira] Closed: (DIREVE-68) Authorization Service: hardcode simple authorization rules for safty

Posted by "Alex Karasulu (JIRA)" <di...@incubator.apache.org>.
     [ http://nagoya.apache.org/jira/browse/DIREVE-68?page=history ]
     
Alex Karasulu closed DIREVE-68:
-------------------------------

    Resolution: Fixed

All done last test and service changes are in revision 56320.

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

> Authorization Service: hardcode simple authorization rules for safty
> --------------------------------------------------------------------
>
>          Key: DIREVE-68
>          URL: http://nagoya.apache.org/jira/browse/DIREVE-68
>      Project: Directory Eve
>         Type: Task
>   Components: interceptors
>     Reporter: Alex Karasulu
>     Assignee: Alex Karasulu

>
> We need to prevent everyone except the admin user from accessing the admin user's entry.  It should not be returned on searches and lookup's should fail if these operations are not being conducted by the admin.  This will prevent other users from being able to read the admin's entry or alter it.  In general I'm not in favor of hard coding rules but this is one that is almost universally valid and is ok to hardcode.  After all this can be changed later as dynamic authorization policy mechanisms are put into place.  Also modifyRdn and delete operations will not be allowed!
> Furthermore we can extend this to regular users where only those that own their entry under ou=users,ou=system can read, or modify their entry.  No modifyRdn, or delete operations are allowed on these entries by any user except the admin user.  The admin user can do anything it wants to do.  Other users besides the creator/owner cannot read the userPassword field.
> This is basically a new interceptor implementation.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://nagoya.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