Is your feature request related to a problem? Please describe.
Looking at the implementation of RBAC-based authorization, the focus always seems to be on the "ID" of elements, e.g. specific submodels can be enabled/disbaled in the registry using the submodelIDs parameter:
{ "role": "basyx-standard-user", "action": "READ", "targetInformation": { "@type": "submodel-registry", "submodelIds": "*" } } .
Is there also the possibility to define roles based on the semanticID of an element? This would be greatly beneficial to allow to show/hide types of submodels instead of needing to manually define the ID of every submodel.
Describe the solution you'd like
Refering to above example, I would like to be able to specify the follwing:
{ "role": "basyx-standard-user", "action": "READ", "targetInformation": { "@type": "submodel-registry", "submodelISemanticds": "*" } } .
Is your feature request related to a problem? Please describe.
Looking at the implementation of RBAC-based authorization, the focus always seems to be on the "ID" of elements, e.g. specific submodels can be enabled/disbaled in the registry using the
submodelIDsparameter:{ "role": "basyx-standard-user", "action": "READ", "targetInformation": { "@type": "submodel-registry", "submodelIds": "*" } }.Is there also the possibility to define roles based on the
semanticIDof an element? This would be greatly beneficial to allow to show/hide types of submodels instead of needing to manually define the ID of every submodel.Describe the solution you'd like
Refering to above example, I would like to be able to specify the follwing:
{ "role": "basyx-standard-user", "action": "READ", "targetInformation": { "@type": "submodel-registry", "submodelISemanticds": "*" } }.