How to extend a firewall protected CLM deployment with a RTC serving as a publicly available issue tracker?
Dear all,
we currently operate CLM behind our company firewall, i.e., user have full access to the system while being connected to the company intranet or from the outside using VPN.
In addition to the internally used CLM, we also operate a publicly accessible issue tracker. The latter needs to be replaced, so the question came up whether this can be achieved using RTC, since we use this as an internal issue tracker anyway.
What we need to achieve is to allow customers to access RTC in order to file and follow progress on their defects, enhancements, etc. while keeping all of the data currently contained in the CLM inaccessible to them. However, internal users shall be able to access this customer provided data alongside the "protected" internal work items. Artefact duplication should be prohibited, though.
My rough idea would be to deploy a second publicly accessible JTS/RTC server, whose PAs will be configured as members of the existing internal CLM projects, which are still protected by being behind the firewall.
Does this sound feasible or does anyone have any ideas how this can be achieved more effectively?
Thanks a lot for your input in advance. Cheers,
Timo.
we currently operate CLM behind our company firewall, i.e., user have full access to the system while being connected to the company intranet or from the outside using VPN.
In addition to the internally used CLM, we also operate a publicly accessible issue tracker. The latter needs to be replaced, so the question came up whether this can be achieved using RTC, since we use this as an internal issue tracker anyway.
What we need to achieve is to allow customers to access RTC in order to file and follow progress on their defects, enhancements, etc. while keeping all of the data currently contained in the CLM inaccessible to them. However, internal users shall be able to access this customer provided data alongside the "protected" internal work items. Artefact duplication should be prohibited, though.
My rough idea would be to deploy a second publicly accessible JTS/RTC server, whose PAs will be configured as members of the existing internal CLM projects, which are still protected by being behind the firewall.
Does this sound feasible or does anyone have any ideas how this can be achieved more effectively?
Thanks a lot for your input in advance. Cheers,
Timo.
Accepted answer
Timo,
On Jazz.net we expose the RTC development for internal and external use. So this can be done.
If you want the users to be able to access your current internal development RTC, you would have to move it - at least a HTTP proxy outside of the firewall - keeping the public URI stable.
You could set up a dedicated RTC server outside the firewall and allow customers access to it and have the internal RTC server befriended to the external one, to be able to create links between the two.
Pleas be aware that RTC has only limited capabilities in data hiding. So depending on what you want external users to see and not to see, you would have to check if RTC can provide you with that.
On Jazz.net we expose the RTC development for internal and external use. So this can be done.
If you want the users to be able to access your current internal development RTC, you would have to move it - at least a HTTP proxy outside of the firewall - keeping the public URI stable.
You could set up a dedicated RTC server outside the firewall and allow customers access to it and have the internal RTC server befriended to the external one, to be able to create links between the two.
Pleas be aware that RTC has only limited capabilities in data hiding. So depending on what you want external users to see and not to see, you would have to check if RTC can provide you with that.
Comments
