Hi @ThibaultM ,
I looked through the Device Bridge snap and the scopes and permissions are defined. It looks to me like they may not quite be adhering to the latest schema requirements. Specifically the note below. There is no service in the main identifier.
Remark: Restrictions apply on the scope namings, identifiers, etc. (see below)
Use the following schema for the main identifier of the scope:
<id>.<service>
id: Package identifier. Has to correspond to the snap name
Example: rexroth-solutions, rexroth-vpnmanager, ...
service: Service identifier
Example: web "scopes-declaration": [
{
"description": "Permissions",
"identifier": "devicebridge",
"name": "DeviceBridge",
"scopes": [
{
"description": "DeviceBridge readonly mode",
"identifier": "devicebridge.all.r",
"name": "ReadOnly"
},
{
"description": "DeviceBridge power user mode",
"identifier": "devicebridge.all.rw",
"name": "Poweruser"
},
{
"description": "Manage and modify Axis configuration",
"identifier": "devicebridge.all.rwz",
"name": "Administrator"
}
]
}
],
Regardless, there is some incompatability with the newer releases of ctrlX OS, that I was able to reproduce.
... View more
