Authorization V2: authorization for products #3926
Conversation
…jo into authorization-2
![accesslint[bot]](https://avatars.githubusercontent.com/in/1502?s=60&v=4){kind=small}
|
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
|
Conflicts have been resolved. A maintainer will review the pull request shortly. |
|
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
|
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
|
Conflicts have been resolved. A maintainer will review the pull request shortly. |
|
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
|
Conflicts have been resolved. A maintainer will review the pull request shortly. |
madchap
added
the
settings_changes
|
I don't see any changes to this PR. The core is pretty stable now and Products and Product Types are complete. When this PR is merged I will continue with Engagements, Tests and Findings. |
Authorization V2: authorization for products (DefectDojo#3926)
With this next step of the new authorization comes the authorization for products. Now we can have product members additionally to product type members. Almost every place where products or product types are used has been adapted to the new authorisation.
And I introduced a new flag in the settings. With this a staff user can get full authorization for all products and product types. This is close to the current behaviour and might be helpful for installations with only a small group of users that are a security team.
Further steps will see the new authorization for engagements, tests, findings and endpoints. There will be not a lot of new code anymore but changes in filters, forms, views and html templates