remote client

[bwhite]

I am about to set up our first remote client to talk to our server here.

The intro says that vault should handle remote clients over the internet
without any problems, but I can't find any discussion about the details.

What do I need to do differently for the client installation?
What do I need to open up on the firewall?

For example, the way I currently set up clients includes giving the machine
name, but I don't expect the local machine name or the 10.0.2... IP address
to be visible from outside the LAN.

A link to an article would be sufficient.

Thanks,
Brad.

[Beth]

The Vault server will be accessible from the internet in much the same way as any other web page. You will need a public IP address that either goes to your server or to a router that will forward to your server. There isn't a document on this because there is more than one way to do this, and this isn't configured through our software. This is a matter of how your server and/or routers are set up to work.

[bwhite]

Um, I can't phrase it like that. 8: -)

a) I'll get shot down for publicly exposing code over the internet.

b) What prevents just anyone from accessing the code?

c) They'll want to lock it down as tightly as possible, so I'll
need to know exactly what I need to open up.

The SOS docs were pretty clear, IIRC.
You don't have anything similar for your flagship?

Thanks,
Brad.

[Beth]

Vault server is an ASP.NET based server which runs under IIS. Some of the things you can use include a VPN, IIS in a DMZ, or port forwarding. How this will work depends on what you would like to put in place. If you have any websites currently available to the internet, you might want to look at how those were set up.

We have an article on the basic Vault security that discusses Vault security: http://support.sourcegear.com/viewtopic.php?p=17672. Your code isn't really just automatically dumped out to the internet with any route you take.

Let's say you want to just port forward like what you saw in the SOS article. You will have a public IP address that comes to your external router. I'll make up a fake one for this example of 100.100.100.100 You could open one of the ports for Fortress, let's say you use port 8888. That means the URL external users would use for the web client would be http://100.100.100.100:8888/vaultservice/vaultweb. On your router, you will forward the port 8888 to your actual server. Let's say your server is 10.10.10.10. You can forward then to 10.10.10.10 and the port number of 80. If you don't want to use 80, you can set up your website to use a port number to, and that is done in your IIS Manager.

[bwhite]

Got it.

Thanks for the details,
Brad.

[Beth]

You're welcome.