You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Enhance multi tenancy support for the secureCodeBox #79
Is your feature request related to a problem? Please describe.
Enhance the multi tenancy support of the secureCodeBox API.
This allows Users to restrict access to ability to see and work on securityTests. This enables Users to scan services located in isolated networks, by restricting the access to Scans to the technical users of the scanner services inside these networks. By restricting the access to the securityTest to the isolated worker it is ensured that no other worker outside this network can "steal" this job.
Describe the solution you'd like
The easiest way to configure multi tenancy is to create multiple camunda tenants (secureCodeBox engine) and assign the technical users to the corresponding tenant. To control to which tenant a securityTest should belong you can set the tenant attribute on the securityTest model, when starting a process.
Note: You need to be a member of the tenant to start a process as part of the tenant. When the tenant attribute is set to null or is not set at all the process will be started without a tenant.
Open Todos:
Add documentation on how multi tenancy works and how to use it
Find & Document a way to prevent tenant works to lock jobs without a tenant. (This should already be possible to do, by setting up the authentication correctly)
Activity
rfelber commentedon Apr 11, 2019
Work in progress: secureCodeBox/engine#79
J12934 commentedon Apr 24, 2019
Docs getting created here:
https://github.com/secureCodeBox/secureCodeBox/tree/docs/multi-tenancy
rfelber commentedon Jan 5, 2020
Hi @J12934 i think we should merge your documentation work here because it is helpful for everyone ;-)
https://github.com/secureCodeBox/secureCodeBox/tree/docs/multi-tenancy
J12934 commentedon Jan 6, 2020
Oh good point.
Forgot that this hasn't been merged yet.
Opened up PR #100