Actions
Feature #23046
open
Runtime constraint to allow network access but not Arvados API access
Status:
New
Priority:
Normal
Assigned To:
-
Category:
API
Target version:
-
Story points:
-
Description
For example, this would be useful for service containers that must listen on the network to function, but do not need to access Arvados and therefore do not need an API token. Following the principle of least privilege, if those containers don't need to access Arvados, they shouldn't get a token.
Propose {"network": true}. It can stay default false as it is now.
No data to display
Actions