MeshCentral - Individual Device Rights, HeapDump
This week a major new update to MeshCentral was published with a single big feature that caused a lot code changes all over the project. Because of this, community testing and feedback is very much appreciated. The big feature is that you can now assign user permissions for individual devices instead of an entire device group. In the past, you created a device group and assigned user rights to that device group. This did not allow individual devices to be singled out. Users have been working about this limitation by creating many different device groups with different user permissions and moving devices between groups. This was far from ideal.
Anytime you change the access control system, it’s a big deal as your changing a lot of code. In addition, with this new release a user can be given access to a single device but not the group that this device belongs to. So, the web application needs to deal with how to display this device. A new “Individual Devices” header will now show up when a user has access to a device but it’s the device group that device belongs to. Because access control to a device can be given in different ways, the sum of all access rights is what the user gets. So, you can now grant limited rights to a device group but grant full access to some of the devices in that group. The web application (desktop and mobile) will both handle this correctly. Controlling device access can be done by clicking on a device, or if you are server administrator, you can click on the “My Users” tab, click a user and edit its device rights on that screen.
In addition to the big feature, this last week MeshCentral got a lot more bug fixes and a new “HeapDump” feature allowing developers to easily and quickly dump the NodeJS heap to a file and read the file using the Chrome browser. This simplifies greatly the task of finding and fixing memory leaks in the server.
Once again, many thanks to the GitHub community for their amazing help. If you see any problems and need support on something, please create a new issue on GitHub or help other users.
Enjoy,
Ylian
Twitter: https://twitter.com/meshcentral
Reddit: https://www.reddit.com/r/MeshCentral/
GitHub: https://github.com/Ylianst/MeshCentral/issues
MeshCentral2: http://www.meshcommander.com/meshcentral2
Anytime you change the access control system, it’s a big deal as your changing a lot of code. In addition, with this new release a user can be given access to a single device but not the group that this device belongs to. So, the web application needs to deal with how to display this device. A new “Individual Devices” header will now show up when a user has access to a device but it’s the device group that device belongs to. Because access control to a device can be given in different ways, the sum of all access rights is what the user gets. So, you can now grant limited rights to a device group but grant full access to some of the devices in that group. The web application (desktop and mobile) will both handle this correctly. Controlling device access can be done by clicking on a device, or if you are server administrator, you can click on the “My Users” tab, click a user and edit its device rights on that screen.
In addition to the big feature, this last week MeshCentral got a lot more bug fixes and a new “HeapDump” feature allowing developers to easily and quickly dump the NodeJS heap to a file and read the file using the Chrome browser. This simplifies greatly the task of finding and fixing memory leaks in the server.
Once again, many thanks to the GitHub community for their amazing help. If you see any problems and need support on something, please create a new issue on GitHub or help other users.
Enjoy,
Ylian
Twitter: https://twitter.com/meshcentral
Reddit: https://www.reddit.com/r/MeshCentral/
GitHub: https://github.com/Ylianst/MeshCentral/issues
MeshCentral2: http://www.meshcommander.com/meshcentral2
