[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Authentication Issue

From: Pape, Barry <Barry.Pape_at_nov.com>
Date: Fri, 13 Jun 2014 18:22:53 +0000

Thanks Johan. The solution ended up being to reset the password in the domain. The odd thing is the user account was fine, not locked and the password was not expired. It had been approximately 90 days since we set the password, so I assume something is going on with the domain settings or user account.

-----Original Message-----
From: Johan Corveleyn [mailto:jcorvel_at_gmail.com]
Sent: Tuesday, June 10, 2014 7:11 PM
To: Pape, Barry
Cc: users_at_subversion.apache.org
Subject: Re: Authentication Issue

On Tue, Jun 10, 2014 at 11:21 PM, Pape, Barry <Barry.Pape_at_nov.com> wrote:
> Hello,
>
>
>
> We have a service account in our domain that we use for our builds. I
> am trying to connect to our Subversion server via the command line:
>
> svn co --username BuildUser --password private --no-auth-cache
> https://svnserver/Repo1/trunk/
>
>
>
> This works fine from my local machine, but from the build server I receive:
>
> svn: E170001: OPTIONS of : authorization failed: Could not
> authenticate to
> server: rejected Basic challenge
>
>
>
>
>
> Any ideas on why this would work on one machine, but not another?
>

The first obvious thing to check is: is it the same version of svn client software? 'svn --version' should tell you.

The second thing: what about the network route? Any proxies, firewalls, ... differences between both network paths?

--
Johan
Received on 2014-06-13 20:23:45 CEST

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.