| << Back to previous view |
|
[QB-1198] Be able to prevent users from accessing build artifacts in child configurations even if they can access parent configuration
|
|
| Status: | Open |
| Project: | QuickBuild |
| Component/s: | None |
| Affects Version/s: | 4.0.26 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major |
| Reporter: | Robin Shen | Assigned To: | Robin Shen |
| Resolution: | Unresolved | Votes: | 1 |
| Remaining Estimate: | Unknown | Time Spent: | Unknown |
| Original Estimate: | Unknown | ||
| Comments |
| Comment by Don Ross [ 21/Aug/15 03:23 PM ] |
|
I have a master configuration 'builds' and under that a configuration for each team. In general, teams need access to each others' build data.
However, I also have a 'test' configuration to which I want to deny all access except to RelEng. I tried to set up permissions for 'Development' as follows: root/builds .... (basic read permissions) root/builds/test ... (blank) But the second setting has no effect. What I am looking for is the ability to set a 'no access' on root/builds/test. The alternative is to set individual access to each project: root/builds/platform ... (basic read permissions) root/builds/client ... (basic read permissions) etc... which means i have to add new permissions when we add a new project. Also, I think it means I can't grant access to the root? |
| Comment by Robin Shen [ 21/Aug/15 10:53 PM ] |
| If authorize user to access a parent configuration, all child configuration will be visible to make the tree easy to construct and understand (this is also necessary for performance reasons), however if you do not specify any permissions for the child configuration, user will not be able to see anything inside it except for the build version and build history. |