← Prev in month ← Prev in thread
Next in thread → Next in month →

[OASIS Issue Tracker] (COEL-46) Requirement to have separate identifiers for the same entity is restrictive and hard to audit.

From
OASIS Issues Tracker <>
Date
2015-11-10T13:20:15+00:00
ID
Thread
[OASIS Issue Tracker] (COEL-46) Requirement to have separate identifiers for the same entity is restrictive and hard to audit.
Paul Bruton created COEL-46:
-------------------------------

             Summary: Requirement to have separate identifiers for the same entity is restrictive and hard to audit.
                 Key: COEL-46
                 URL: https://issues.oasis-open.org/browse/COEL-46
             Project: OASIS Classification of Everyday Living (COEL) TC
          Issue Type: Bug
            Reporter: Paul Bruton


·         RPE 4.3.1.4 says we SHALL have different userids and passwords for each embodiment. In practice this means that a service provider or operator will have more than one ID. This is fundamentally un-inspectable and tricky to get your head around. It means that the Operator needs three OperatorIDs and the Service Provider needs two ServiceProviderIDs. I think this is a MAY for increased security not a SHALL.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
← Prev in month ← Prev in thread
Next in thread → Next in month →