Uploaded image for project: 'IoTivity'
  1. IoTivity
  2. IOT-1437

Additional ACL functionality needed to develop ACL-based group management in D2S communication

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Undecided
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: IoTivity 1.2.0
    • Component/s: Build System
    • Labels:
      None
    • Found in Version/s:
      1.2RC
    • Issue Severity:
      Critical
    • Reproducibility:
      Always (100%)

      Description

      Additional ACL functionality is needed to develop ACL-based group management.

      1. addAclACE() is needed to return generated ACE ID list
      When a device is added to a group, multiple ACE entities are registered to the device ACL, where the number of ACE entities are decided based on the number of users in the group.
      There is the “public void addAclACE(String aclid, List<HashMap<String, Object>> aclist)” to add ACEs. However, when an aclist [ACE1, ACE2, ACE3] is added to the device ACL and [ACEID_A, ACEID_B, ACEID_C] is generated, it is hard to recognize that the id “ACEID_A” corresponds to ACE1. Thus, I ask you to modify addAclACE() to return the generated ACE ID list (ex: as a List to represent
      [

      {“aceid”:“ace1412”, “subjectuuid”:”u2”, …}

      ,

      {“aceid”:“ace1413”, “subjectuuid”:”u3”, …}

      ]
      ).
      2. Throughout the ACL management logic,

      {href : “*”}

      is needed to be considered as “all resources” in the ACL verify logic.
      For example, when a device is registered to the group, each ACE needs to be added to each device ACL according to the group ACL. The group ACL is usually declared as “[{“permission”: 15, “resources”: [

      {“href”: ”*”, “rt”: [“”], “if”: [“oic.if.baseline”]}

      ]}].

        Attachments

          Activity

            People

            • Assignee:
              sunil.k14 sunil kumar k r
              Reporter:
              yeonghun.nam Yeonghun Nam
            • Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: