Hey there,
Thank you for this report! Since it seems that you’re in a local testing environment, you can actually attach a debugger to your server instance to see what’s coming up null here. Let me know if that’s at all possible. Can you also share your device manager configuration? FWIW, there’s nothing too extravagant going on with Horde’s device manager - as it’s effectively a keyvalue pair to list kits, and track if they’re in use or not.
>And one more question: is there a way to restrict the permission to create new entries in the Device Manager? Even with zero claims, I was still able to add new devices.
You should be able to control this via the DeviceWrite ACL Action (Action list here). There isn’t specific pool controls per-se, but more so project scoped pools (and the resulting ACL for that project), and for global, you require either admin or “Internal-Employees” user claim role. In short:
- You must have DeviceRead or DeviceWrite ACLs on at least one project in the pool’s ProjectIds (Project Scope)
- You must have “Internal-Employees” user claim role or have AdminWrite.
To review a user’s claim/entitlement set, you can do so in the User profile (or via /api/v1/account/entitlements). This is of course assuming you have authentication enabled.
Kind regards,
Julian