René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Enhance multi tenancy support for the secureCodeBox","articleBody":"**Is your feature request related to a problem? Please describe.**\r\nEnhance the multi tenancy support of the secureCodeBox API.\r\n\r\nThis 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.\r\n\r\n**Describe the solution you'd like**\r\nThe 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. \r\n\r\n\u003e 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.\r\n\r\nOpen Todos:\r\n\r\n- [x] Add documentation on how multi tenancy works and how to use it\r\n- [x] Find \u0026 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)","author":{"url":"https://github.com/rfelber","@type":"Person","name":"rfelber"},"datePublished":"2019-04-11T09:47:59.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":4},"url":"https://github.com/79/secureCodeBox/issues/79"}