[ 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
