I have implemented the "Level" attribute into a driver to test out.
To test it out I have implemented it in the following way with 16 being the read param and 116 as the write param.
<Param id="16" Level="5" trending="false">
<Name>timezone</Name>
<Param id="116" Level="5" snmpSetAndGet="true">
<Name>timezone</Name>
I then added the security level to a few different users and groups to test the new feature. Admins have a Level 1; Advanced users have Level 5, standard users with Level 6 and basic users with Level 8.
So with the Level 5 attribute, I should only be able to read and write with level 1 and 5 users and not for the rest. But unfortunately, I can still access and write a value to the parameters as a level 8 user.
Besides including the Level="" in the param line and the Group or user level, is there anywhere else this needs to be changed for the feature to work?
Also, is the level attribute different to the ownership attribute?
Hi Nathan,
I have been trying to reproduce the behavior you encountered but cannot reproduce this behavior so far. Could you verify if my setup matches your setup?
I have created this basic driver with 4 read/write params each with its own level:
The element looks like this for an Administrator:
I have an Administrators group, with level 1.
A level 5 group, with level 5.
A level 10 group, with level 10.
All groups have users with the default group level inherited from the group.
For the level 5 user, the level 1 parameter is correctly hidden. The level 5, 10 and 20 parameters are still visible.
The same is true for the level 10 user.
So far this all looks correct to me.
Now I set a group level override to 1 for the level 5 user and 15 for the level 10 user.
The level 5 user, can now see the level 1 parameter (as expected by the overridden level). This test confirms you can grant users more access by overriding the group level.
Now the level 10 user can only see the level 20 parameter, meaning it's also possible to grant users fewer permissions by overriding the group level.
I am testing this on the latest 10.2.7 version, which version are you running?
Hi Jens,
Now that we are running on Cube 10.2, the level function is working as intended.
I have been able to hide particular parameters from users and display and restrict the ability to make changes unless the user is on a high level.
This works great!
Glad to hear it works now!
Hi Jens.
Thank you for your response.
I have tested this in Cube 9.5 (We are upgrading soon) and Cube 10.2 (test system as part of the upgrade.)
I will have another play today and see where I get.