Requestor Web App and https

9 views
Skip to first unread message

Chad Peterson

unread,
Nov 2, 2010, 5:29:42 PM11/2/10
to VersionOne-users
Does the requester web app have the ability to connect to a VersionOne
instance that is located on a secure server... (i.e.
https://my.version.one.server.com/mysite)

I know I've had to play certificate tricks to make this work on with
the APIClient, but I'm totally unfamiliar with the ObjectModel API
(which is used by the Requestor application).

I'm not an IT guru either... I just want to know if anyone's
successfully done this, before I go hunting down said guru.

Thanks in advance!

Roger Vaughn

unread,
Nov 4, 2010, 1:02:49 PM11/4/10
to VersionOne-users
Yes it can, absolutely. You don't have to play certificate tricks with
it - under the covers it uses the same sort of code a web browser
would use to talk to an HTTPS website. You *do* have to configure it
with a login and password to your VersionOne instance though - and for
this you will either have to use your admin login or use a licensed
user with at least the global Requestor role.

Chad Peterson

unread,
Nov 5, 2010, 4:10:48 PM11/5/10
to VersionOne-users
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).

Chad Peterson

unread,
Nov 5, 2010, 4:12:45 PM11/5/10
to VersionOne-users
And, I apologize if this was the wrong group to post to. Just realized
that there is a "dev" group over at http://groups.google.com/group/versionone-dev.

On Nov 4, 12:02 pm, Roger Vaughn <roger.a.vau...@gmail.com> wrote:
Reply all
Reply to author
Forward
0 new messages