-
### What we have:
- One big acl for the whole application, where everything is put into:
- Route access rules
- Controller/action access rules
- Resource (Entity) access rules
- Special assert…
TiSiE updated
7 years ago
-
# Current Behavior
When Webapi is setup with e.g. OIDC and a new User signs in, it defaults to the `public` role. Without any preparation on the database, an admin has to set the actual roles afterwa…
-
### Description:
The current logic is hardcoded to add "master,data,ingest" roles to the nodes added while scaling up.
### Expectation:
Read this node role from the user in the config.yaml file
-
Currently, we hardcode the management endpoint `/management` when assigning the roles in default server configuration.
We need to make sure we assign the appropriate role for the management context…
-
Currently TBotD is designed to run on TBD. This has good reasons, of course, but it would be nice to figure out how to reduce that dependency as much as possible, and to figure out where it still exis…
-
Moved to here from #2876
Current Wekan permissions are [Admin/BoardAdmin/NoComments/CommentOnly/Worker](https://github.com/wekan/wekan/wiki/REST-API-Role). Current permissions are hardcoded with ch…
-
Currently the upribox software uses a hardcoded network range for clients:
`192.168.55.0/24`
In certain cases the default network might overlap with already existing (local/remote) networks.
Rewo…
-
**Is your feature request related to a problem? Please describe.**
When application_type is resource_server, users can define a custom claimToAuthorityPrefix (defaults to "APPROLE_") with the propert…
-
It would be helpful to control which fields are persisted and which ones aren't when cloning new CEs.
The ones that are currently hardcoded to copy are:
* collector roles
* georeferences
* start…
-
### Expected behavior
As an administrator of application I would like to be able to configure what field will be imported from AD during AD synchronisation between ATLAS roles and AD groups.
### A…