Thanks for your response!
However, we've tried all of that. But, when running through IIS and
trying to connect to an https:// server, it does not seem to work.
Confirmed proper user, and proper password. Logged in as the same
user that the web-server runs as, it can access and connect to our
https://versionone_server without issue (after I installed proper
server authentication certificates for our environment).
Example keys we're using in the config:
<add key="authenticationType" value="WindowsIntegrated" />
<add key="v1Url" value="
https://server/project" />
<add key="username" value="user@domain" />
The username has proper permissions in the instance we're trying to
connect to.
The IIS web site is set up to run as the doman\username account with
appropriate password.
When accessing the requestor website, this is the resultant error
message: "The configured Url could not be used to access VersionOne.”
Any additional thoughts in light of this error? (we've contacted
VersionOne support directly, but thought I'd throw it out here as
well).