PID scoped Accounts

[ashcherbakov]

Provide account access keys that are scoped to a range of product ID’s (PIDs).
Currently account access keys are scoped to vendor ID’s (VID) only. See

• https://github.com/zigbee-alliance/distributed-compliance-ledger/blob/master/proto/dclauth/account.proto#L22
• https://github.com/zigbee-alliance/distributed-compliance-ledger/blob/master/x/model/keeper/check_model_rights.go#L9

If a PID is specified for the account, then the account can manage Model/ModelVersion with the given PID only (similar to VID scoped Accounts).

Example:

• Vendor Account Key 1: 0x ABC…. , VID = 0x 1111, PID [0000 - 0011] (OPTIONAL)
• Vendor Account Key 2: 0x DEF…. , VID = 0x 1111, PID [0012 - 1111] (OPTIONAL)
• Vendor Account Key 3: 0x AEF…. , VID = 0x 1111
  Once approved, Key1 will only be able to create/update records (model/modelversions) with VID = 0x 1111, PID [0000 - 0011]. Key3 can create/update all records (model/modelversions). If the PID ranges are submitted, they are enforced to be non-overlapping.

Acceptance Criteria:

• Extend the Account with a new optimal field(s)
  • modify .proto files (https://github.com/zigbee-alliance/distributed-compliance-ledger/blob/master/proto/dclauth/account.proto#L22)
  • regenerate the code, see https://github.com/zigbee-alliance/distributed-compliance-ledger/blob/master/README-DEV.md#how-to-make-changes-in-data-model-for-existing-modules
• Extend the business logic (https://github.com/zigbee-alliance/distributed-compliance-ledger/blob/master/x/model/keeper/check_model_rights.go ?) to check for PIDs when creating/updating/deleting a Model or ModelVersion.
• Add Unit Tests. Consider improving/simplifying existing unit tests if it makes sense. Create tests for both positive and negative scenarios.
  • https://github.com/zigbee-alliance/distributed-compliance-ledger/blob/master/x/model/handler_test.go
  • https://github.com/zigbee-alliance/distributed-compliance-ledger/blob/master/x/model/types/messages_model_test.go
  • https://github.com/zigbee-alliance/distributed-compliance-ledger/blob/master/x/model/types/messages_model_version_test.go
• Add Integration tests (CLI and REST). Positive and basic negative tests (to check that errors are returned) are enough.
• Update docs
  • https://github.com/zigbee-alliance/distributed-compliance-ledger/blob/master/docs/transactions.md
  • https://github.com/zigbee-alliance/distributed-compliance-ledger/blob/master/docs/how-to.md

[ashcherbakov]

PR: #530

[akarabashov]

• Functionality implemented as described in the ticket
• Unit and integration tests are added
• Docs are updated.