Setup Multiple Independant Projects In One RTC Instance.
Hi,
Our situation is similar to Gary Dang's from this thread:
https://jazz.net/forums/viewtopic.php?t=1078
but different enough I thought it warrented its own topic.
We also also like to host multiple independant projects which should ideally have no visibility into each other.
We were hoping to run one jazz server and just assign resources to their projects. However, looking at below line from the Jazz Deployment Guide that is not the case.
'In release 1.0 all users have read access to all data on the server even if they are not formally a member of a specific Project Area. If you must limit access to a project then you should plan to host that Project Area exclusively on it is own Jazz Team Server.'
Is the only way to mitigate this to incur the overhead of multiple Jazz Servers? Does the development team know if this is something that is going to be updated in the near term?
Allen Carley
Ascendant Technology
Our situation is similar to Gary Dang's from this thread:
https://jazz.net/forums/viewtopic.php?t=1078
but different enough I thought it warrented its own topic.
We also also like to host multiple independant projects which should ideally have no visibility into each other.
We were hoping to run one jazz server and just assign resources to their projects. However, looking at below line from the Jazz Deployment Guide that is not the case.
'In release 1.0 all users have read access to all data on the server even if they are not formally a member of a specific Project Area. If you must limit access to a project then you should plan to host that Project Area exclusively on it is own Jazz Team Server.'
Is the only way to mitigate this to incur the overhead of multiple Jazz Servers? Does the development team know if this is something that is going to be updated in the near term?
Allen Carley
Ascendant Technology
One answer
In order to enforce strict visibility rules you need to utilize multiple
servers. This issue will not be solved in the near term, i.e. in a
maintenance release, but is considered for the next major release.
Kai
Jazz PMC
acarley wrote:
servers. This issue will not be solved in the near term, i.e. in a
maintenance release, but is considered for the next major release.
Kai
Jazz PMC
acarley wrote:
Hi,
Our situation is similar to Gary Dang's from this thread:
https://jazz.net/forums/viewtopic.php?t=1078
but different enough I thought it warrented its own topic.
We also also like to host multiple independant projects which should
ideally have no visibility into each other.
We were hoping to run one jazz server and just assign resources to
their projects. However, looking at below line from the Jazz
Deployment Guide that is not the case.
'In release 1.0 all users have read access to all data on the server
even if they are not formally a member of a specific Project Area. If
you must limit access to a project then you should plan to host that
Project Area exclusively on it is own Jazz Team Server.'
Is the only way to mitigate this to incur the overhead of multiple
Jazz Servers? Does the development team know if this is something
that is going to be updated in the near term?
Allen Carley
Ascendant Technology