Multiple VIS-2 editor and runtime entries, uncertainty with user/admin access
I'm looking for a solution to let externals access only my VIS-2 runtime only as own user/ no admin. Maybe I missed s.th., understood s.th. wrong, still it doesn't work. Here my story:
I disabled admin access to admin.0 and admin.1 instance access and access is not possible anymore (404 error) I've installed latest version of adapters.
When i login iobroker.pro, i now see 2 entries for VIS-2 editor and 3 entries for VIS-2 runtime, 1 entry each leads to a "404 remote answer" failure, the others are successful. What worries me most, is the successful access to VIS-2 editor with admin access, although i have removed read/write access for the external user in VIS-2 project. I have also raised a ticket for VIS-2 yesterday, not sure if it belongs to web or VIS-2 component.
However, i do not understand why there a multiple entries and how to prevent the external user access components like editors for VIS-2 but also for FLOT.
To Reproduce
- create external user with users group
- create admin.1 and web.1 instance and configure them to use no authorization and external user
- login iobroker.pro
Expected behavior
Ideally would be to see only VIS-2 runtime, since access to all other components is not possible. At least i expect not to be able to access any editor to change configuration.
Thanks in advance.
Regards padman
When i login iobroker.pro is this a problem about local or cloud access?
I use cloud access
The cloud service accesses vis(-2) and admin only as "admin" user (and all other adapters). It is not designed for non-admins.
Thank you for the hint with the admin user. Do you have an idea why vis-2 instances pop up 2 or 3 times since last cloud/web adapter update as shown in my screenshot.
Regards padman