Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "HR Directory Access Control Policy"
(→See Also) |
|||
Line 2: | Line 2: | ||
[[Image:Higgins_logo_76Wx100H.jpg|right]] | [[Image:Higgins_logo_76Wx100H.jpg|right]] | ||
− | [[Image:Access-control-use-cases-hr- | + | [[Image:Access-control-use-cases-hr-v3.png]] |
== Notes == | == Notes == | ||
Line 8: | Line 8: | ||
* A new diagramming style is used--it is more compact at representing the literal attributes of an Entity within a single rectangular box. | * A new diagramming style is used--it is more compact at representing the literal attributes of an Entity within a single rectangular box. | ||
* The entire use case now fits on one diagram (just barely!) | * The entire use case now fits on one diagram (just barely!) | ||
− | * The new '' | + | * The new ''groupSubject'' higgins:subject sub-attribute is now being used |
− | * A new '' | + | * A new ''selfInstanceSubject'' higgins:subject sub-attribute is now being used. This is what allows us to have the subject of the policy be the Entity that represents the IdAS consumer |
* See [[HOWL Update 1.1.104]] for related changes to support this use case | * See [[HOWL Update 1.1.104]] for related changes to support this use case | ||
− | |||
− | |||
− | |||
− | |||
==See Also== | ==See Also== | ||
* [http://wiki.eclipse.org/Access_Control_Use_Cases#HR_directory (this) HR Directory use case] | * [http://wiki.eclipse.org/Access_Control_Use_Cases#HR_directory (this) HR Directory use case] | ||
* all [[Access Control Use Cases]] | * all [[Access Control Use Cases]] |
Revision as of 20:40, 13 July 2008
{{#eclipseproject:technology.higgins}}
File:Access-control-use-cases-hr-v3.png
Notes
The above is a second (v2) attempt at modeling this use-case.
- A new diagramming style is used--it is more compact at representing the literal attributes of an Entity within a single rectangular box.
- The entire use case now fits on one diagram (just barely!)
- The new groupSubject higgins:subject sub-attribute is now being used
- A new selfInstanceSubject higgins:subject sub-attribute is now being used. This is what allows us to have the subject of the policy be the Entity that represents the IdAS consumer
- See HOWL Update 1.1.104 for related changes to support this use case