RE: Can a different user name/password be supplied with the API connection when VersionOne is set to use Windows Integrated Authentication?

208 views
Skip to first unread message

Acey Bunch

unread,
Jun 21, 2012, 8:37:10 AM6/21/12
to version...@googlegroups.com

Eric,

 

The APIClient documentation provides examples of how to connect to a VersionOne instance using Windows authentication, and it can be found here: http://community.versionone.com/sdk/DetailedDocumentation/SDK%20.Net/apiclient/apiclient.html#lbe.setup.V1Auth.

 

There are basically two approaches, one using the credentials of the user that is currently logged in, the other using their fully qualified domain name.

 

Have you tried those?

 

Acey Bunch

Technical Product and Agile Consultant

VersionOne

 

From: version...@googlegroups.com [mailto:version...@googlegroups.com] On Behalf Of Eric
Sent: Wednesday, June 20, 2012 3:51 PM
To: version...@googlegroups.com
Subject: Can a different user name/password be supplied with the API connection when VersionOne is set to use Windows Integrated Authentication?

 

I'm trying to run a scheduled job using the API on a windows server but since the instance of VersionOne I am trying to connect to is configured to use Windows Integrated Authentication it is trying to connect as the server windows user, which of course is not a member on VersionOne.  I supplied the windows user name and password of a valid VersionOne member but it seems to ignore it and continues to give me a security exception "com.versionone.apiclient.SecurityException: User Not Authorized".

 

I get the security exception with either one:

 

V1APIConnector dataConnector = new V1APIConnector(url, userName, password);
V1Instance v1 = new V1Instance(applicationPath, userName, password);

--
You received this message because you are subscribed to the Google Groups "VersionOne-dev" group.
To view this discussion on the web visit https://groups.google.com/d/msg/versionone-dev/-/kRhjIfoBJ3oJ.
To post to this group, send email to version...@googlegroups.com.
To unsubscribe from this group, send email to versionone-de...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/versionone-dev?hl=en.

Acey

unread,
Jun 21, 2012, 2:45:13 PM6/21/12
to version...@googlegroups.com
This sounds like an issue for VersionOne support.

You can contact them at sup...@versionone.com.


On Thursday, June 21, 2012 8:44:58 AM UTC-4, Eric wrote:
Yes, I have attempted to try that.  But their documentation seems to be out of date.  I downloaded the latest jars and the V1APIConnector doesn't even have a constructor with a signature for supplying a boolean to indicate to use windows authentication or not.  I have supplied a fully qualified username and password and it still attempts to connect as the user that is logged into windows.

To post to this group, send email to versionone-dev@googlegroups.com.
To unsubscribe from this group, send email to versionone-dev+unsubscribe@googlegroups.com.

Raynard

unread,
Jan 30, 2014, 2:45:58 AM1/30/14
to version...@googlegroups.com
Hi!

I am experiencing the same problem with you right now. I also tried using the different approaches to connecting to VersionOne.

I would just like to know, how this was resolved or fixed?

Thank you!

Regards,
Raynard

ibuchanan

unread,
Feb 3, 2014, 8:50:35 AM2/3/14
to version...@googlegroups.com
Raynard,

To clear something up, it is possible to use different credentials with SDK.NET API Client, but not with SDK.Java API Client. At present, the HTTP client used in the Java code is not sophisticated enough to handle the nuances of NTLM well enough to support impersonation. We have tried to move to the Apache HTTP Client but the coupling to the old Sun client has made this very difficult. That code is still on a branch, not yet in any released jars.

Ian Buchanan
Product Manager for Platform and Integrations
Reply all
Reply to author
Forward
0 new messages