permissions #10

Closed
opened 7 years ago by lub · 1 comments
lub commented 7 years ago
Owner

permit a specific matrix user for one or multiple commands

permit a specific matrix user for one or multiple commands
pandro added the
Feature
label 7 years ago
pandro added the
Important
label 7 years ago
lub added this to the Milestone 1: Basic command set milestone 7 years ago
lub commented 7 years ago
Poster
Owner

I think it makes sense to be able to grant permissions on all levels:

  1. all - omnipotent admin user. not sure about this as it promotes bad practices (principle of least privilege)
  2. project
  3. service
  4. subcommand
  5. args

I'd suggest a regex for configuring what is allowed on a specific level. Lookup wise it would iterate through all levels from top to bottom and if a user has the permission level configured match the configured regex. If it matches grant access, otherwise don't.

Also edited the OP to only matrix user for the moment. See #23 for group permissions.

I think it makes sense to be able to grant permissions on all levels: 0. all - omnipotent admin user. not sure about this as it promotes bad practices (principle of least privilege) 1. project 2. service 3. subcommand 4. args I'd suggest a regex for configuring what is allowed on a specific level. Lookup wise it would iterate through all levels from top to bottom and if a user has the permission level configured match the configured regex. If it matches grant access, otherwise don't. Also edited the OP to only matrix user for the moment. See #23 for group permissions.
lub referenced this issue from a commit 7 years ago
lub closed this issue 7 years ago
lub referenced this issue from a commit 7 years ago
This repo is archived. You cannot comment on issues.
No Assignees
1 Participants
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: lubiland/heimdall#10
Loading…
There is no content yet.