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
authz-db=authz
2.这个参数值表示密码数据库的文件名称,如conf下的 passwd 文件。
password-db = passwd
使用conf下的配置文件时,这些参数值要和conf下的配置文件名称相同。
svn: E215004: Authentication failed相关推荐
- git配置报错fatal: Authentication failed for ‘‘问题解决
git配置报错fatal: Authentication failed for ''问题解决 参考文章: (1)git配置报错fatal: Authentication failed for ''问题 ...
- 客户端svn出现authorization failed异常
客户端svn出现authorization failed异常 参考文章: (1)客户端svn出现authorization failed异常 (2)https://www.cnblogs.com/ox ...
- 遇到问题:push的时候出现fatal: Authentication failed for
GitHub push代码发生错误:fatal: Authentication failed for 'https://github.com/ - 使用的https提交,在用SourceTree提交代 ...
- mongodb php 报错,PHP5 mongodb 切换db报错 Authentication failed on database admin-汗血宝马
权限 已经开启,在test上创建了用户test1,并赋予了 test的readWrite 和 reporting的read权限. { "_id" : "test.test ...
- WCF分布式开发常见错误(26):Authentication failed
这个也是WCF分布式安全开发实践过程里常见的错误. 验证失败,因为远端已经关闭传输流. WCF 传输安全模式下,客户端和服务器端使用证书进行验证.WSHttpBinding.启动服务宿主程序 ...
- git中fatal: Authentication failed的问题
今天从git上down项目输错了一次账户和密码,然后就怎么也down不下来,直接报错,到处清除缓存,都没啥作用,实在是无奈,搞得人火大,最后终于在一篇文章找到了解决方法 fatal: Authenti ...
- 【rabbitmq】Authentication failed (rejected by the remote node), please check the Erlang cookie
前言 erlang 23.1 rabbitmq server v3.8.9 win 10 问题描述 使用 rabbitmqctl 命令时出现错误: C:\Program Files\RabbitMQ ...
- Git push “fatal: Authentication failed ”
Git push "fatal: Authentication failed " 问题原因 之前设置了两步验证 If you enabled two-factor authenti ...
- TortoiseGit拉取或推送,输入账号密码后提示 HTTP Basic: Access denied fatal: Authentication failed 解决方案...
TortoiseGit拉取或推送项目,输入账号密码后,提示 HTTP Basic: Access denied fatal: Authentication failed. 大体意思是,HTTP基本认证 ...
最新文章
- 共享单车哈罗王炸连出,OFO小心沦为炮灰
- 测试tcp连接数工具_后端开发程序员不知道压力测试怎么能行
- C# GDI+编程(二)
- php7.2 swoole_loader,用什么方法可以让swoolec-loader支持php7.3?
- Python-学习-import语句导入模块
- hystrix断路器引发的相关概念
- Threejs性能监视和可视化控制
- 给定一个0-1串,请找到一个尽可能长的子串,其中包含的0与1的个数相等。
- 操作系统知识点大总结【进线程管理与调度】
- 简述static关键字、void与void *(void指针)、函数指针
- ITIL是什么意思?ITIL是什么?
- navicat win32注册机下载 | 绿色版
- cp正在写入文件导致文件内容不一致
- (第六章)UI--PS 基础 图层蒙版与混合模式
- matlab 的滤波器分析,滤波器matlab分析
- 高云FPGA系列教程(2):FPGA点灯工程创建、程序下载和固化
- K-D 树, 高维空间索引
- Java基础学习生疏知识点总结(4)——面向对象、单一职责原则、this关键字、构造方法
- 软件测试——逻辑覆盖
- 用linux扫描网络设备,Linux网络扫描和嗅探工具—Nmap命令
热门文章
- Spring高级程序设计(Spring框架创始人倾情推荐的权威开发指南)
- elasticSearch6源码分析(6)http和transport模块
- h5py快速入门指南
- Vue、React、Angular最佳UI框架
- js对html进行转义和反转义的操作
- Centos7安装mariadb galera cluster数据库集群 详解
- [EMC++] Item 8. Prefer nullptr to 0 and NULL
- 我在OSC的第一篇博文
- 【SSM框架系列】Spring - JdbcTemplate声明式事务
- fastadmin弹框提示不起作用 confirm