Login | Register
My pages Projects Community openCollabNet

Discussions > users [DISABLED] > Re: --non-interactive causing auth failure?

subversion
Discussion topic

Hide all messages in topic

All messages in topic

Re: --non-interactive causing auth failure?

Author David Abrahams <dave at boostpro dot com>
Full name David Abrahams <dave at boostpro dot com>
Date 2009-04-08 13:37:55 PDT
Message on Wed Apr 08 2009, David Abrahams <dave-AT-boostpro.com> wrote:

> David Abrahams <dave <at> boostpro.com> writes:
>
>>
>> I can "svn up" and it works fine without asking for any passwords, but
>> when I "svn up --non-interactive", I get
>>
>> svn: OPTIONS of 'https://my-server/and/path': authorization failed:
>> Could not authenticate to server: rejected Basic challenge
>> (https://my-server)
>
> It turns out that when I remove the auth cache and update again, Subversion
> tells me that the server certificate isn't trusted:
>
> Error validating server certificate for 'https://my-server:443':
> * The certificate is not issued by a trusted authority. Use the
> fingerprint to validate the certificate manually!
> Certificate information:
> * Hostname: my-server
> * Valid: from Mon, 23 Jun 2008 00:00:00 GMT until Sat, 23 Jun 2012 23:59:59
> GMT
> * Issuer: Network Solutions L.L.C., US
> * Fingerprint: f5:3e:6a:3c:4c:dd:4b​:18:6c:4b:4e:23:7d:d​b:38:10:89:32:f3:7d
>
> This doesn't seem right. Network Solutions should be a trusted authority,
> shouldn't it? I'm on MacOSX with MacPorts, FWIW.

Well, I solved that trust issue (https://svn.macports​.org/ticket/19247),
but I *still* get the "rejected Basic challenge" message when I use
--non-interactive. Help, anybody?

--
Dave Abrahams
BoostPro Computing
http://www.boostpro.com

Re: --non-interactive causing auth failure?

Author David Abrahams <dave at boostpro dot com>
Full name David Abrahams <dave at boostpro dot com>
Date 2009-04-08 12:59:22 PDT
Message David Abrahams <dave <at> boostpro.com> writes:

>
> I can "svn up" and it works fine without asking for any passwords, but
> when I "svn up --non-interactive", I get
>
> svn: OPTIONS of 'https://my-server/and/path': authorization failed:
> Could not authenticate to server: rejected Basic challenge
> (https://my-server)

It turns out that when I remove the auth cache and update again, Subversion
tells me that the server certificate isn't trusted:

Error validating server certificate for 'https://my-server:443':
 * The certificate is not issued by a trusted authority. Use the
   fingerprint to validate the certificate manually!
Certificate information:
 * Hostname: my-server
 * Valid: from Mon, 23 Jun 2008 00:00:00 GMT until Sat, 23 Jun 2012 23:59:59
 GMT
 * Issuer: Network Solutions L.L.C., US
 * Fingerprint: f5:3e:6a:3c:4c:dd:4b​:18:6c:4b:4e:23:7d:d​b:38:10:89:32:f3:7d

This doesn't seem right. Network Solutions should be a trusted authority,
shouldn't it? I'm on MacOSX with MacPorts, FWIW.

--
Dave Abrahams
BoostPro Computing
http://boostpro.com

--non-interactive causing auth failure?

Author David Abrahams <dave at boostpro dot com>
Full name David Abrahams <dave at boostpro dot com>
Date 2009-04-08 09:13:55 PDT
Message I can "svn up" and it works fine without asking for any passwords, but
when I "svn up --non-interactive", I get

  svn: OPTIONS of 'https://my-server/and/path': authorization failed:
  Could not authenticate to server: rejected Basic challenge (https://my-server)

Is this a known problem? Anyone have a workaround?

TIA,

--
Dave Abrahams
BoostPro Computing
http://www.boostpro.com
Messages per page: