You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The SDKs and CLI all support the is_accessible_by_support_until__date device property on balena-cloud to grant/deny balena support access to SSH and various other config updates, but is_accessible_by_support_until__date doesn't seem to be implemented anywhere in open-balena-api. Is there an equivalent in open-balena?
The use case here is that some open-balena devices are deployed in end-customer environments and the end-customer needs to be able to decide when the open-balena admin (and team) should be allowed to access SSH and other config. Obviously we could strip SSH keys from end devices when it shouldn't be allowed, but there doesn't seem to be a way to put them back.
Hi @shaunco ,
No, open-balena doesn't offer anything equivalent to is_accessible_by_support_until__date.
In open-balena all users have access to all devices and all orgs of the system. Isolated organizations, access levels and support access are only implemented/supported in balenaCloud & balenaMachine.
The SDKs and CLI all support the
is_accessible_by_support_until__date
device property on balena-cloud to grant/deny balena support access to SSH and various other config updates, butis_accessible_by_support_until__date
doesn't seem to be implemented anywhere in open-balena-api. Is there an equivalent in open-balena?The use case here is that some open-balena devices are deployed in end-customer environments and the end-customer needs to be able to decide when the open-balena admin (and team) should be allowed to access SSH and other config. Obviously we could strip SSH keys from end devices when it shouldn't be allowed, but there doesn't seem to be a way to put them back.
Seems like the
is_accessible_by_support_until__date
check should be in https://github.com/balena-io/open-balena-api/blob/master/src/features/host-os-access/access.tsThe text was updated successfully, but these errors were encountered: