svn: E215004: Authentication failed

简介:

Linux环境配置安装好SVN服务器后,输入命令:

svn co svn:// IP : PORT

结果返回Authentication failed

[root]@iZ23whn33Z conf]#svn co svn://115.29.250.111:3690

svn:E215004:Unable to connect to a repository at URL 'svn://115.29.250.111'

svn:E215004:Authentication failed


可能出现这种问题的原因:

(1)配置文件中出现前缀空格符

(2)配置文件中配置参数异常

(3)后续再补充

针对第一种问题,解决办法如下:把需要配置的参数前缀空格都去除

[root@iZ23whn33jnZ ~]# cd /usr/local/svn/mbk/conf/
[root@iZ23whn33jnZ conf]# ll
total 16
-rw-r--r-- 1 root root 1114 Jan 26 11:27 authz
-rw-r--r-- 1 root root  331 Jan 26 11:27 passwd
-rw-r--r-- 1 root root 3058 Jan 26 11:32 svnserve.conf
[root@iZ23whn33jnZ conf]# vi svnserve.conf

### This file controls the configuration of the svnserve daemon, if you
### use it to allow access to this repository.  (If you only allow
### access through http: and/or file: URLs, then this file is
### irrelevant.)


### Visit http://subversion.apache.org/ for more information.


[general]
### The anon-access and auth-access options control access to the
### repository for unauthenticated (a.k.a. anonymous) users and
### authenticated users, respectively.
### Valid values are "write", "read", and "none".
### Setting the value to "none" prohibits both reading and writing;
### "read" allows read-only access, and "write" allows complete
### read/write access to the repository.
### The sample settings below are the defaults and specify that anonymous
### users have read-only access to the repository, while authenticated
### users have read and write access to the repository.
anon-access = none
auth-access = write
### The password-db option controls the location of the password
### database file.  Unless you specify a path starting with a /,
### the file's location is relative to the directory containing
### this configuration file.
### If SASL is enabled (see below), this file will NOT be used.
### Uncomment the line below to use the default password file.
password-db = passwd
### The authz-db option controls the location of the authorization
### rules for path-based access control.  Unless you specify a path
### starting with a /, the file's location is relative to the the
### directory containing this file.  If you don't specify an
### authz-db, no path-based access control is done.
### Uncomment the line below to use the default authorization file.
authz-db=authz
### This option specifies the authentication realm of the repository.
### If two repositories have the same authentication realm, they should
### have the same password database, and vice versa.  The default realm
### is repository's uuid.
realm=mbk
### The force-username-case option causes svnserve to case-normalize
### usernames before comparing them against the authorization rules in the
### authz-db file configured above.  Valid values are "upper" (to upper-
### case the usernames), "lower" (to lowercase the usernames), and
### "none" (to compare usernames as-is without case conversion, which
### is the default behavior).
force-username-case = none


[sasl]
### This option specifies whether you want to use the Cyrus SASL
### library for authentication. Default is false.
### This section will be ignored if svnserve is not built with Cyrus
### SASL support; to check, run 'svnserve --version' and look for a line
### reading 'Cyrus SASL authentication is available.'
# use-sasl = true
### These options specify the desired strength of the security layer
### that you want SASL to provide. 0 means no encryption, 1 means
### integrity-checking only, values larger than 1 are correlated
### to the effective key length for encryption (e.g. 128 means 128-bit
### encryption). The values below are the defaults.
# min-encryption = 0
# max-encryption = 256



PS : conf下面的几个配置文件都要去除前缀空格。

针对第二种问题,解决办法如下:检查配置的参数是否正确
1.这个参数值表示认证的配置文件名称,如conf下的 authz 文件。
authz-db=authz

2.这个参数值表示密码数据库的文件名称,如conf下的 passwd 文件。

password-db = passwd

使用conf下的配置文件时,这些参数值要和conf下的配置文件名称相同。

相关文章
|
7月前
|
Unix 数据安全/隐私保护
|
3月前
|
数据安全/隐私保护
github报错(完美解决):获取token。remote: Support for password authentication was removed on August 13, 2021.
这篇文章介绍了如何在GitHub上解决因密码认证被移除而导致的推送错误,通过创建和使用个人访问令牌(token)来代替密码进行身份验证。
455 0
|
5月前
|
网络安全 开发工具 数据安全/隐私保护
Win10使用Git克隆项目出现fatal: Authentication failed for异常
Windows 10系统中使用Git克隆项目时出现"fatal: Authentication failed for"异常的解决方法,主要是通过修改凭据管理器中的Git凭据密码来解决因密码过期导致的身份验证失败问题。
99 0
Win10使用Git克隆项目出现fatal: Authentication failed for异常
|
5月前
|
Ubuntu 开发工具 git
ubuntu 14.04的git 错误: gnutls_handshake() failed: Handshake failed
本文提供了一个解决Ubuntu 14.04系统上使用Git时遇到的"gnutls_handshake() failed: Handshake failed"错误的脚本,通过替换git的默认加密传输库gnutls为更稳定的openssl,并指导如何编译安装新版本的git来解决问题。
114 0
|
7月前
svn: E175002: Commit failed (details follow): svn: E175002: Unexpected HTTP status 502Bad Gateway on
svn: E175002: Commit failed (details follow): svn: E175002: Unexpected HTTP status 502Bad Gateway on
188 1
|
7月前
|
数据安全/隐私保护
remote: 认证失败,请确认您输入了正确的账号密码。 fatal: Authentication failed
、remote: 认证失败,请确认您输入了正确的账号密码。 fatal: Authentication failed
|
8月前
|
缓存 开发工具 git
Git Cloning into :error: RPC failed
Git Cloning into :error: RPC failed
119 0
|
开发工具 数据安全/隐私保护 git
Authentication failed for 错误
Authentication failed for 错误
258 0
|
开发工具 数据安全/隐私保护 git
git 报错:Support for password authentication was removed. Please use a personal access token instead.
git 报错:Support for password authentication was removed. Please use a personal access token instead.
397 0
git 报错:Support for password authentication was removed. Please use a personal access token instead.
|
开发工具 git
git remote: Permission to denied
git remote: Permission to denied
261 0
git remote: Permission to denied

相关实验场景

更多