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 2005/10/31 09:14:55 UTC
[jira] Created: (DIREVE-297) [Access Control] Autonomous areas for AC must not overlap
[Access Control] Autonomous areas for AC must not overlap
----------------------------------------------------------
Key: DIREVE-297
URL: http://issues.apache.org/jira/browse/DIREVE-297
Project: Directory Server
Type: Bug
Reporter: Alex Karasulu
Assigned to: Alex Karasulu
Fix For: 0.9.4
Presently the subentry subsystem associates entries with all selecting subentries regardless of autonomous area demarcations. What this means is AAA's can overlap. When the AP of an accessControlSpecificArea is the decendent of the AP of another accessControlSpecificArea those areas should not intersect such that the subentries of the first area do not effect entries of the second area. This is not the case. The subentry subsystem associates entries with effecting subentires without checking to see if those subentries are in a different AAA in these configurations where an AAA is under another AAA.
We need to track all AP of AAA's within the system. Before associating an entry with an AP's subentries checks should be made to determine under which AAA the entry resides. Only those subentries associated with that AAA should be associated with the entry.
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DIRSERVER-257) [Access Control] Autonomous areas
for AC must not overlap
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRSERVER-257?page=all ]
Alex Karasulu updated DIRSERVER-257:
------------------------------------
Fix Version: 1.0-RC2
(was: 1.0-RC1)
Version: 1.0-RC1
(was: pre-1.0)
> [Access Control] Autonomous areas for AC must not overlap
> ---------------------------------------------------------
>
> Key: DIRSERVER-257
> URL: http://issues.apache.org/jira/browse/DIRSERVER-257
> Project: Directory ApacheDS
> Type: Bug
> Versions: 1.0-RC1
> Reporter: Alex Karasulu
> Assignee: Alex Karasulu
> Fix For: 1.0-RC2
>
> Presently the subentry subsystem associates entries with all selecting subentries regardless of autonomous area demarcations. What this means is AAA's can overlap. When the AP of an accessControlSpecificArea is the decendent of the AP of another accessControlSpecificArea those areas should not intersect such that the subentries of the first area do not effect entries of the second area. This is not the case. The subentry subsystem associates entries with effecting subentires without checking to see if those subentries are in a different AAA in these configurations where an AAA is under another AAA.
> We need to track all AP of AAA's within the system. Before associating an entry with an AP's subentries checks should be made to determine under which AAA the entry resides. Only those subentries associated with that AAA should be associated with the entry.
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DIRSERVER-257) [Access Control] Autonomous areas
for AC must not overlap
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSERVER-257:
----------------------------------------
Fix Version/s: (was: 1.5.5)
2.0.0-RC1
Postponed to 2.0.0-RC1
> [Access Control] Autonomous areas for AC must not overlap
> ---------------------------------------------------------
>
> Key: DIRSERVER-257
> URL: https://issues.apache.org/jira/browse/DIRSERVER-257
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: core
> Affects Versions: 1.5.0, 1.0.2
> Reporter: Alex Karasulu
> Assignee: Alex Karasulu
> Priority: Trivial
> Fix For: 2.0.0-RC1
>
>
> Presently the subentry subsystem associates entries with all selecting subentries regardless of autonomous area demarcations. What this means is AAA's can overlap. When the AP of an accessControlSpecificArea is the decendent of the AP of another accessControlSpecificArea those areas should not intersect such that the subentries of the first area do not effect entries of the second area. This is not the case. The subentry subsystem associates entries with effecting subentires without checking to see if those subentries are in a different AAA in these configurations where an AAA is under another AAA.
> We need to track all AP of AAA's within the system. Before associating an entry with an AP's subentries checks should be made to determine under which AAA the entry resides. Only those subentries associated with that AAA should be associated with the entry.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRSERVER-257) [Access Control] Autonomous areas
for AC must not overlap
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRSERVER-257?page=all ]
Alex Karasulu updated DIRSERVER-257:
------------------------------------
Fix Version/s: 1.1.0
(was: 1.0-RC4)
Affects Version/s: 1.0-RC2
1.0-RC3
1.0-RC4
Priority: Minor (was: Major)
For now this is acceptable. Until we get users using the standard single AA configuration we should not be worried about this. It's so minor. If users really want this to follow full X.500 standards we can fix this.
> [Access Control] Autonomous areas for AC must not overlap
> ---------------------------------------------------------
>
> Key: DIRSERVER-257
> URL: http://issues.apache.org/jira/browse/DIRSERVER-257
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: core
> Affects Versions: 1.0-RC1, 1.0-RC2, 1.0-RC3, 1.0-RC4
> Reporter: Alex Karasulu
> Assigned To: Alex Karasulu
> Priority: Minor
> Fix For: 1.1.0
>
>
> Presently the subentry subsystem associates entries with all selecting subentries regardless of autonomous area demarcations. What this means is AAA's can overlap. When the AP of an accessControlSpecificArea is the decendent of the AP of another accessControlSpecificArea those areas should not intersect such that the subentries of the first area do not effect entries of the second area. This is not the case. The subentry subsystem associates entries with effecting subentires without checking to see if those subentries are in a different AAA in these configurations where an AAA is under another AAA.
> We need to track all AP of AAA's within the system. Before associating an entry with an AP's subentries checks should be made to determine under which AAA the entry resides. Only those subentries associated with that AAA should be associated with the entry.
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (DIRSERVER-257) [Access Control] Autonomous areas
for AC must not overlap
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRSERVER-257?page=all ]
Alex Karasulu updated DIRSERVER-257:
------------------------------------
Component: core
> [Access Control] Autonomous areas for AC must not overlap
> ---------------------------------------------------------
>
> Key: DIRSERVER-257
> URL: http://issues.apache.org/jira/browse/DIRSERVER-257
> Project: Directory ApacheDS
> Type: Bug
> Components: core
> Versions: 1.0-RC1
> Reporter: Alex Karasulu
> Assignee: Alex Karasulu
> Fix For: 1.0-RC2
>
> Presently the subentry subsystem associates entries with all selecting subentries regardless of autonomous area demarcations. What this means is AAA's can overlap. When the AP of an accessControlSpecificArea is the decendent of the AP of another accessControlSpecificArea those areas should not intersect such that the subentries of the first area do not effect entries of the second area. This is not the case. The subentry subsystem associates entries with effecting subentires without checking to see if those subentries are in a different AAA in these configurations where an AAA is under another AAA.
> We need to track all AP of AAA's within the system. Before associating an entry with an AP's subentries checks should be made to determine under which AAA the entry resides. Only those subentries associated with that AAA should be associated with the entry.
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DIRSERVER-257) [Access Control] Autonomous areas
for AC must not overlap
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Karasulu updated DIRSERVER-257:
------------------------------------
Fix Version/s: (was: 1.5.0)
> [Access Control] Autonomous areas for AC must not overlap
> ---------------------------------------------------------
>
> Key: DIRSERVER-257
> URL: https://issues.apache.org/jira/browse/DIRSERVER-257
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: core
> Affects Versions: 1.0-RC4, 1.0-RC3, 1.0-RC2, 1.0-RC1
> Reporter: Alex Karasulu
> Assigned To: Alex Karasulu
> Priority: Trivial
>
> Presently the subentry subsystem associates entries with all selecting subentries regardless of autonomous area demarcations. What this means is AAA's can overlap. When the AP of an accessControlSpecificArea is the decendent of the AP of another accessControlSpecificArea those areas should not intersect such that the subentries of the first area do not effect entries of the second area. This is not the case. The subentry subsystem associates entries with effecting subentires without checking to see if those subentries are in a different AAA in these configurations where an AAA is under another AAA.
> We need to track all AP of AAA's within the system. Before associating an entry with an AP's subentries checks should be made to determine under which AAA the entry resides. Only those subentries associated with that AAA should be associated with the entry.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRSERVER-257) [Access Control] Autonomous areas
for AC must not overlap
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alex Karasulu updated DIRSERVER-257:
------------------------------------
Fix Version/s: (was: 1.5.3)
1.5.5
> [Access Control] Autonomous areas for AC must not overlap
> ---------------------------------------------------------
>
> Key: DIRSERVER-257
> URL: https://issues.apache.org/jira/browse/DIRSERVER-257
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: core
> Affects Versions: 1.5.0, 1.0.2
> Reporter: Alex Karasulu
> Assignee: Alex Karasulu
> Priority: Trivial
> Fix For: 1.5.5
>
>
> Presently the subentry subsystem associates entries with all selecting subentries regardless of autonomous area demarcations. What this means is AAA's can overlap. When the AP of an accessControlSpecificArea is the decendent of the AP of another accessControlSpecificArea those areas should not intersect such that the subentries of the first area do not effect entries of the second area. This is not the case. The subentry subsystem associates entries with effecting subentires without checking to see if those subentries are in a different AAA in these configurations where an AAA is under another AAA.
> We need to track all AP of AAA's within the system. Before associating an entry with an AP's subentries checks should be made to determine under which AAA the entry resides. Only those subentries associated with that AAA should be associated with the entry.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRSERVER-257) [Access Control] Autonomous areas
for AC must not overlap
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSERVER-257:
----------------------------------------
Fix Version/s: (was: 1.0.3)
(was: 1.5.2)
1.5.3
Postponed.
> [Access Control] Autonomous areas for AC must not overlap
> ---------------------------------------------------------
>
> Key: DIRSERVER-257
> URL: https://issues.apache.org/jira/browse/DIRSERVER-257
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: core
> Affects Versions: 1.0.2, 1.5.0
> Reporter: Alex Karasulu
> Assignee: Alex Karasulu
> Priority: Trivial
> Fix For: 1.5.3
>
>
> Presently the subentry subsystem associates entries with all selecting subentries regardless of autonomous area demarcations. What this means is AAA's can overlap. When the AP of an accessControlSpecificArea is the decendent of the AP of another accessControlSpecificArea those areas should not intersect such that the subentries of the first area do not effect entries of the second area. This is not the case. The subentry subsystem associates entries with effecting subentires without checking to see if those subentries are in a different AAA in these configurations where an AAA is under another AAA.
> We need to track all AP of AAA's within the system. Before associating an entry with an AP's subentries checks should be made to determine under which AAA the entry resides. Only those subentries associated with that AAA should be associated with the entry.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRSERVER-257) [Access Control] Autonomous areas
for AC must not overlap
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSERVER-257:
----------------------------------------
Affects Version/s: (was: 1.0-RC3)
(was: 1.0-RC4)
(was: 1.0-RC2)
(was: 1.0-RC1)
1.0.2
1.5.0
Fix Version/s: 1.0.3
1.5.2
Postponed to 1.0.3 and 1.5.2
> [Access Control] Autonomous areas for AC must not overlap
> ---------------------------------------------------------
>
> Key: DIRSERVER-257
> URL: https://issues.apache.org/jira/browse/DIRSERVER-257
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: core
> Affects Versions: 1.0.2, 1.5.0
> Reporter: Alex Karasulu
> Assignee: Alex Karasulu
> Priority: Trivial
> Fix For: 1.5.2, 1.0.3
>
>
> Presently the subentry subsystem associates entries with all selecting subentries regardless of autonomous area demarcations. What this means is AAA's can overlap. When the AP of an accessControlSpecificArea is the decendent of the AP of another accessControlSpecificArea those areas should not intersect such that the subentries of the first area do not effect entries of the second area. This is not the case. The subentry subsystem associates entries with effecting subentires without checking to see if those subentries are in a different AAA in these configurations where an AAA is under another AAA.
> We need to track all AP of AAA's within the system. Before associating an entry with an AP's subentries checks should be made to determine under which AAA the entry resides. Only those subentries associated with that AAA should be associated with the entry.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRSERVER-257) [Access Control] Autonomous areas
for AC must not overlap
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny updated DIRSERVER-257:
----------------------------------------
Issue Type: Improvement (was: Bug)
Fix Version/s: 2.1.0
(was: 2.0.0-RC1)
This is due to the fact we don't currently support Inner AP. All our AAA are IAP in fact.
I don't think we can fix that for 2.0, I would rather do it for 2.1.
Note that it's a problem that can be worked around by adding a chopAfter restriction, where the DN used on the chopAfter is the lower AP DN.
> [Access Control] Autonomous areas for AC must not overlap
> ---------------------------------------------------------
>
> Key: DIRSERVER-257
> URL: https://issues.apache.org/jira/browse/DIRSERVER-257
> Project: Directory ApacheDS
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.5.0, 1.0.2
> Reporter: Alex Karasulu
> Assignee: Alex Karasulu
> Priority: Trivial
> Fix For: 2.1.0
>
>
> Presently the subentry subsystem associates entries with all selecting subentries regardless of autonomous area demarcations. What this means is AAA's can overlap. When the AP of an accessControlSpecificArea is the decendent of the AP of another accessControlSpecificArea those areas should not intersect such that the subentries of the first area do not effect entries of the second area. This is not the case. The subentry subsystem associates entries with effecting subentires without checking to see if those subentries are in a different AAA in these configurations where an AAA is under another AAA.
> We need to track all AP of AAA's within the system. Before associating an entry with an AP's subentries checks should be made to determine under which AAA the entry resides. Only those subentries associated with that AAA should be associated with the entry.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIRSERVER-257) [Access Control] Autonomous areas
for AC must not overlap
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRSERVER-257?page=all ]
Alex Karasulu updated DIRSERVER-257:
------------------------------------
Fix Version: 1.0-RC3
(was: 1.0-RC2)
> [Access Control] Autonomous areas for AC must not overlap
> ---------------------------------------------------------
>
> Key: DIRSERVER-257
> URL: http://issues.apache.org/jira/browse/DIRSERVER-257
> Project: Directory ApacheDS
> Type: Bug
> Components: core
> Versions: 1.0-RC1
> Reporter: Alex Karasulu
> Assignee: Alex Karasulu
> Fix For: 1.0-RC3
>
> Presently the subentry subsystem associates entries with all selecting subentries regardless of autonomous area demarcations. What this means is AAA's can overlap. When the AP of an accessControlSpecificArea is the decendent of the AP of another accessControlSpecificArea those areas should not intersect such that the subentries of the first area do not effect entries of the second area. This is not the case. The subentry subsystem associates entries with effecting subentires without checking to see if those subentries are in a different AAA in these configurations where an AAA is under another AAA.
> We need to track all AP of AAA's within the system. Before associating an entry with an AP's subentries checks should be made to determine under which AAA the entry resides. Only those subentries associated with that AAA should be associated with the entry.
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DIRSERVER-257) [Access Control] Autonomous areas
for AC must not overlap
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRSERVER-257?page=all ]
Alex Karasulu updated DIRSERVER-257:
------------------------------------
Fix Version: 1.0-RC4
(was: 1.0-RC3)
> [Access Control] Autonomous areas for AC must not overlap
> ---------------------------------------------------------
>
> Key: DIRSERVER-257
> URL: http://issues.apache.org/jira/browse/DIRSERVER-257
> Project: Directory ApacheDS
> Type: Bug
> Components: core
> Versions: 1.0-RC1
> Reporter: Alex Karasulu
> Assignee: Alex Karasulu
> Fix For: 1.0-RC4
>
> Presently the subentry subsystem associates entries with all selecting subentries regardless of autonomous area demarcations. What this means is AAA's can overlap. When the AP of an accessControlSpecificArea is the decendent of the AP of another accessControlSpecificArea those areas should not intersect such that the subentries of the first area do not effect entries of the second area. This is not the case. The subentry subsystem associates entries with effecting subentires without checking to see if those subentries are in a different AAA in these configurations where an AAA is under another AAA.
> We need to track all AP of AAA's within the system. Before associating an entry with an AP's subentries checks should be made to determine under which AAA the entry resides. Only those subentries associated with that AAA should be associated with the entry.
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (DIRSERVER-257) [Access Control] Autonomous areas
for AC must not overlap
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRSERVER-257?page=all ]
Alex Karasulu updated DIRSERVER-257:
------------------------------------
Priority: Trivial (was: Minor)
Really this is trivial.
> [Access Control] Autonomous areas for AC must not overlap
> ---------------------------------------------------------
>
> Key: DIRSERVER-257
> URL: http://issues.apache.org/jira/browse/DIRSERVER-257
> Project: Directory ApacheDS
> Issue Type: Bug
> Components: core
> Affects Versions: 1.0-RC1, 1.0-RC2, 1.0-RC3, 1.0-RC4
> Reporter: Alex Karasulu
> Assigned To: Alex Karasulu
> Priority: Trivial
> Fix For: 1.1.0
>
>
> Presently the subentry subsystem associates entries with all selecting subentries regardless of autonomous area demarcations. What this means is AAA's can overlap. When the AP of an accessControlSpecificArea is the decendent of the AP of another accessControlSpecificArea those areas should not intersect such that the subentries of the first area do not effect entries of the second area. This is not the case. The subentry subsystem associates entries with effecting subentires without checking to see if those subentries are in a different AAA in these configurations where an AAA is under another AAA.
> We need to track all AP of AAA's within the system. Before associating an entry with an AP's subentries checks should be made to determine under which AAA the entry resides. Only those subentries associated with that AAA should be associated with the entry.
--
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
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (DIREVE-297) [Access Control] Autonomous areas for AC must not overlap
Posted by "Alex Karasulu (JIRA)" <di...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/DIREVE-297?page=comments#action_12356387 ]
Alex Karasulu commented on DIREVE-297:
--------------------------------------
Note that this bug makes AAA's under other AAA's behave like inner administrative areas.
> [Access Control] Autonomous areas for AC must not overlap
> ---------------------------------------------------------
>
> Key: DIREVE-297
> URL: http://issues.apache.org/jira/browse/DIREVE-297
> Project: Directory Server
> Type: Bug
> Reporter: Alex Karasulu
> Assignee: Alex Karasulu
> Fix For: 0.9.4
>
> Presently the subentry subsystem associates entries with all selecting subentries regardless of autonomous area demarcations. What this means is AAA's can overlap. When the AP of an accessControlSpecificArea is the decendent of the AP of another accessControlSpecificArea those areas should not intersect such that the subentries of the first area do not effect entries of the second area. This is not the case. The subentry subsystem associates entries with effecting subentires without checking to see if those subentries are in a different AAA in these configurations where an AAA is under another AAA.
> We need to track all AP of AAA's within the system. Before associating an entry with an AP's subentries checks should be made to determine under which AAA the entry resides. Only those subentries associated with that AAA should be associated with the entry.
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira