[OASIS Issue Tracker] (OSLCCORE-82) Propose method for access context discovery

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

James Amsden commented on OSLCCORE-82:
--------------------------------------

However, the overhead of managing another OASIS document/specification is quite high. And the primary use of AccessContext, as limited as they are, is to enable TRS consumer configured access control on TRS provider resources. 

I think the implication of AccessContext is that it corresponds to the unit of user/group access control provided by the server for its managed resources. This often corresponds to the service provider, and is the project area for the jazz-apps. The fact that this correspondence doesn't carry any of the user information to the TRS consumer seems to be a significant functionality gap, one that the jazz-apps close with a synchronizer between LQE and the CLM servers. 

There are also other access control standards that could be adopted, like using LDAP or WebDAV.

This probably needs a lot of thought. Decoupling from TRS might be a good idea. But it significantly leaves open the question of how access control is managed. 

Note that although OSLC Core does provide normative guidance on HTTP authentication, it doesn't mention access control. So perhaps this is ok for TRS too.

> Propose method for access context discovery
> -------------------------------------------
>
>                 Key: OSLCCORE-82
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-82
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Bug
>          Components: TRS
>            Reporter: Martin Sarabura
>            Assignee: Axel Reichwein
>            Priority: Major
>              Labels: TRS
>
> Currently I believe we don't specify how to discover access contexts in our Tracked Resource Specification. We need to fill this gap.



--
This message was sent by Atlassian JIRA
(v7.7.2#77003)