In this quick tutorial, we will cover Understanding the Set Permission Rights Node. In this tutorial, you will learn about the Set Permission Rights Node and how it’s used in Catenis Flow.
In this video we will cover:
Prerequisite
After watching Understanding the Set Permission Rights Node, feel free to watch the next video, Working with the Set Permission Rights Node in Run-Time Mode, to further expand your knowledge.
Subscribe to our channel for more Bitcoin Blockchain building videos! https://www.youtube.com/c/BlockchainofThings
Links from this video for easy access:
To sign up for your free account, head to our website www.blockchainofthings.com.
Join our community forum for the quickest response time to all your questions and concerns. This forum is our customer support. https://forum.blockchainofthings.com/
[Music]
Hi, this is Claire for Blockchain of Things.
In this tutorial, you will learn about the Set Permission Rights Node
and how it’s used in Catenis Flow.
If you haven’t yet watched these two tutorials,
pause the video now, and watch them.
Then come back to this link.
The Set Permission Rights Node sets the permission rights for
a specific permission event on the virtual device issuing the request.
The subject controls its own permissions as to whether or not
any other devices have the capacity to perform a permissioned event with it.
All permissions are set from the perspective of the virtual device issuing the request.
Drag a Set Permission Rights Node into the workspace.
Name the node using the name field
and set a Catenis Virtual Device in the connection field.
There are 14 Catenis Flow fields on the properties panel of this node.
The first field is the events field.
You can review these options by going back to the tutorial
titled “Permission Events” which you can see here:
The System Right field allows you to control the “allow” or “deny” Permission Rights
that you will be applying to the Permission Event you select.
The Allowed Catenis Node indices field can be used to allow access to given Permission Events
across all Catenis Nodes that are listed in this field.
The Denied Catenis Node indices field can be used to deny access to given Permission Events
across all Catenis Nodes that are listed in this field.
The Clear Catenis Node indices field clears any previously
set permissions for a given Permission Event
at the Catenis Node level.
The special wildcard character, “*”, can be used in the Clear Catenis Node indices field
to indicate that the rights for all Catenis Nodes should be removed.
Since each Catenis Node can have many clients,
we can use the Allowed Client IDs to set which clients are allowed by ID.
A client is a structural unit within a Catenis Node.
You can specify the clients across a node that are allowed the Permissioned Event by listing each client ID.
The Denied Client IDs field is the opposite of the Allowed Client ID’s field
and allows you to specify the clients across a node
that are denied the Permissioned Event by listing each client ID.
The Clear Client ID’s field clears any previously set permissions for a given Permission Event at the Catenis Node client level.
The special wildcard character, *, can also be used in the clear Catenis Node indices field
to indicate that the rights for all clients should be removed.
The Allowed Device ID’s field enables you to set allow access to a given Permission Event
across all Catenis Devices, that are listed in this field.
The Allowed Device Product Unique ID field is used to allow access to a given
Permission Event across all Catenis Devices that use a product unique ID in this field.
Use the Denied Device ID field to deny access to a given Permission Event
across all Catenis Devices that are listed in this field.
Use the Denied Device Product Unique ID field to allow access to a given Permission Event
across all Catenis Devices that use a product unique ID in this field.
Use the Clear Device ID field to clear all permissions that
you have previously set for a given Permission Event using device IDs.
Use the Clear Device Product Unique ID field to clear all permissions that you have previously set for a given Permission Event using device product unique IDs
The special wildcard character, *, can also, be used in the Clear Device ID field,
or in the Clear Device Product Unique ID field
to indicate that the rights for all devices should be removed.
Now, let’s take a look at the example flow found at this link:
Copy the example flow.
Click the Node-RED hamburger menu and click import to display the import flow dialog box.
Paste the flow into the import box and click the import button.
This flow is a working example implementing the Set Permission Rights Node.
Note, that after importing the example flow, you will need to set the Catenis Flow Nodes to your own previously configured virtual device.
Note, that inputs injected into Catenis Flow Nodes
containing alternate node properties
will override the properties set on the node slide-out properties panel.
You can pause this tutorial now, to explore this flow on your own.
And in the next video, you’ll learn how to create this flow from scratch.
Excellent!
Now you should understand Set Permission Rights Nodes.
In our next video, you’ll learn how to use this node
in RunTime Mode.
[Music]