So this:
/usr/local/bin/svn up --force --no-auth-cache --username my_user
works fine (after I supply a password). While this:
/usr/local/bin/svn up --force --no-auth-cache --non-interactive --username my_name --password my_pass
depending on the svn version returns:
svn: E215004: Authentication failed and interactive prompting is disabled; see the --force-interactive option
svn: E215004: Unable to connect to a repository at URL 'https://my_repository'
svn: E215004: No more credentials or we tried too many times.
Authentication failed
for Subversion 1.8.8 and:
svn: OPTIONS of 'https://my_repository': authorization failed (https://my_repository)
for Subversion 1.6.11.
All this is on the command line (bash) on a Fedora server.
Also this happens for some users and not others (we have svn users who can run with --non-interactive and others who can not, although their passwords are accepted when I run without --non-interactive). I tried deleting the ~/.subversion/auth/ directory and it properly gets recreated when I do svn up
with credentials.
Pretty stumped at this point. Our repository provider advised we play with the
--trust-server-cert
option but I just get no response (errors or other messages) when I do:
/usr/local/bin/svn up --force --no-auth-cache --non-interactive --quiet --username my_name --password my_pass --trust-server-cert ~/.subversion/auth_iii/svn.ssl.server/my_cert
Appreciate your help...
False alarm. Turns out we had an unescaped ampersand in the password and that was throwing the whole thing off when in a script (this is why pasting the password when prompted worked). Feel stupid now...
Thanks everyone who read and replied...
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With