OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

oslc-core message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (OSLCCORE-68) Extend access context to support notion of delegation


    [ https://issues.oasis-open.org/browse/OSLCCORE-68?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63478#comment-63478 ] 

James Amsden commented on OSLCCORE-68:
--------------------------------------

Scenario:
1. 1000 ChangeRequests have an access context AC1
2. they all need to be change to a different access context AC2
3. add the acc:delegated: AC2 to change them all in one operation

can delegate the delegate, handle loops same as HTTP forwarding and redirects.

[ ] Non-normative note - that AC1 should have its access control properties removed if it is delegated to ensure clients that do not know about delegation do not get the wrong access.

[ ] Clients can choose to ignore access contexts, or treat them in other ways. Unaware clients may do incorrect access.

Servers that provide TRS are giving up access controls, and are only providing hints to well-behaved clients. Allows TRS clients to be able to choose to apply consistent access control using whatever mechanisms they decide. MAY or SHOULD, not MUST

Nick will update the example to not use poor practice in naming the URI.


> Extend access context to support notion of delegation
> -----------------------------------------------------
>
>                 Key: OSLCCORE-68
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-68
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Bug
>            Reporter: Nick Crossley
>            Assignee: James Amsden
>
> There are examples of scenarios where the access context of a large number of resources is affected by an external change.  For example, in a task tracking system, you might need to update the access for a large number of tasks if the work is reassigned to a different release, or to a different team.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]