It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,837
×26

question asked: Mar 16 '16, 7:51 p.m.
question was seen: 1,752 times
last updated: Mar 31 '16, 10:07 p.m.

Related questions

Extend Source Control beyond our firewall?

0
Kenneth Herrscher (12●3●13) | asked Mar 16 '16, 7:51 p.m.
We need to be able to extend the Source Control features of RTC 6.0.1 beyond our firewall so that our Vendors can access a URL from our public website, and check out and upload documents to our CCM Project.

Has anyone already accomplished this feat?

If so, how did you do it, and what would you do differently if you had to do it again?

Thanks much!

One answer

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Ralph Schoon (63.3k●3●36●46) | answered Mar 17 '16, 4:37 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
I think this has been done by many users. The main point here is that the external users have to be able to  access the RTC server using the public URI that is configured for it. So it is either possible to get there directly from outside e.g. by reaching the proxy that hosts the public URI, or by using a VPN tunnel that allows the access.

I am not the network security guy, I think you want to talk to them about what they learned over time.

One suggestion is to always put a caching proxy between the build farm and the RTC server(s).
Comments
Kenneth Herrscher commented Mar 31 '16, 5:31 p.m.

Not sure what this entails. Can you please elaborate further?

Donald Nong commented Mar 31 '16, 10:07 p.m.

Which part is unclear to you? This involves quite a bit networking so you need to have some knowledge about it.

Using VPN is probably the easiest way. Once the vendors authenticate through the VPN (and pass through the firewall), they are effectively "in" your private network (which is "behind" the firewall), and can work in the same way as the employees. If you ever work from home and need to access your company's network, you should know about this.

The other approach is open your RTC instance to the public (internet), just like the jazz.net sandboxes. Of course the server is also open for attacks at the same time. So you need to have sufficient network infrastructures to back it up. Also, in this case, your RTC public URI should have an FQDN that's registered on the Internet, not just your company's DNS.

The last bit about caching proxy is for increasing performance. The basic idea is that the proxy is close to, or local to the vendors so that the latency can be significantly reduced.

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.