Replies: 8 comments 15 replies
-
Currently the UI handles all the permissions and roles. I don’t plan to have any agent specific logic because that would break remote clients. I would rather support this at the user level. Similar how authentication supports filter, it would make sense to also support roles for shell and actions. |
Beta Was this translation helpful? Give feedback.
-
Can I use filters to restrict access to actions and shell? |
Beta Was this translation helpful? Give feedback.
-
It would be convenient to use filters for users. |
Beta Was this translation helpful? Give feedback.
-
Not right now. If more people upvote then I can work on it. Moving to discussion. You can also send PR. |
Beta Was this translation helpful? Give feedback.
-
@amir20 What if we leave the filters only for filtering containers, as they are now, and use rbac for permissions? If we add our own filters to the user, they will interfere with the display of containers, and we need to be able to hide part of the UI. Or do you have a different idea? |
Beta Was this translation helpful? Give feedback.
-
Something like this
and in the user |
Beta Was this translation helpful? Give feedback.
-
I am still testing this a little. I think I want to do some clean up before releasing. |
Beta Was this translation helpful? Give feedback.
-
Released. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the feature you would like to see
I would like to be able to control the activation of actions and shell for specific agents. At the moment, if enabled globally, then all agents have actions or shell enabled.
Describe how you would like to see this feature implemented
Use the existing variables DOZZLE_ENABLE_ACTIONS and DOZZLE_ENABLE_SHELL but on the agent itself
Describe any alternatives you've considered
No response
Beta Was this translation helpful? Give feedback.
All reactions