SSL for HTTPS Remote vs Local no SSL, VS2005 VAULT 4.0.4

vdumas2000 · Post by **vdumas2000** » Mon Nov 12, 2007 11:23 am

Developping in .NET with VAULT 4.0.4.

We have internal and external developpers and to minimize load on the server we have been trying vault with SSL remote access and SSL off for internal access.

The problem is that the bindings contain the SSL configuration

<SccAuxPath>http:...
OR
<SccAuxPath>https:...

This lead to changing the value of "SccAuxPath" all the time in the CSPROJ when the solution is opened from changing location (remote or local).

That leaves us to only once choice: using SSL all the time.

I have no solution to propose, but is it mandatory for your client to contain the prefix HTTPS or HTTP?

Could this work ? : <SccAuxPath>[IP or URL Suffix]/VaultService</SccAuxPath>

Beth · Post by **Beth** » Mon Nov 12, 2007 3:52 pm

Do you know if you are using the MCSCCI interface (VS 2003 compatible client) or the VSIP interface (VS 2005 client)?

What type of project is this?