Authorization Failed error accessing SVN on CentOS 8

[Nate]

I'm getting "Error: Authorization failed" when accessing SVN freshly installed on CentOS 8.

My only clue is that the header on the TortoiseSVN "Commit" screen is "svn://MyDomain.com/ScriptStuff(ATL)/trunk" when in fact the repository was installed at "var/svn" on the CentOS server hosting "MyDomain.com".

I'd be obliged if someone can spot my misstep or knowledgeably speculate on why the realm set to ScriptStuff in the server somehow morphed into "ScriptStuff(ATL)" in the TortoiseSVN commit screen on Windows 10.

Here's what I did starting with installing SVN on CentOS 8 and ending with accessing the remote CentOS server using TortoiseSVN on Windows 10:

1) In CentOS 8 as root used "svnadmin create /var/svn" to create repository at /var/svn

2) In CentOS 8 as root started the svnserve daemon: "svnserve -d -r /var/svn"

3) In CentOS 8 as rootEdited /var/svn/conf/svnserve.conf to include:
auth-access = read
auth-access = write
password-db = passwd
...authz-db = authz
realm = ScriptStuff

4) In CentOS 8 as root edited /var/svn/conf/passwd "[users]" block to include:
User1 = UsrPasswd

5) In Windows 10 using Mozilla (FireFox) tested successfully with "http://MyDomain.com:3690/

6) In Windows 10 using Windows Explorer launched TortoiseSVN Settings/Network with:
Enable Proxy Server checked
Server address set to "svn://MyDomain.com/ScriptStuff"
Username set to "User1"
Password set to "UsrPasswd"


7) In Windows 10 when I right click on a directory in Windows Explorer to upload the directory to the repository using "SVN Commit", the heading reads:
svn://MyDomain.com/ScriptStuff(ATL)/trunk

8) Continuing the commit process in Windows 10 I get "Error: Authorization failed" even when flushing the TortoiseSVN Saved Data and signing in manually with:
Username as "User1"
Password as "UsrPasswd"

Your thoughts and comments will be appreciated!

Nate I. 6/12/2018

[Stefan]

If authorization failed, that means that authentication succeeded (i.e., the server accepted your username/password), but the user you've authenticated with has no authorization to do what you want. Meaning your user doesn't have read/write access to the repository.

[natu...@itsabogus.name]

Stefan wrote:
>> Meaning your user doesn't have read/write access to the repository.

I suppose that where I got confused. TortoiseSCN connects to "svn://MyDomain.com/ScriptStuff". "MyDomain.com" is a server user "mydomain". "ScriptStuff" is the SVN realm from /var/svn/conf/svnserve.conf.

All the files in /var/svn/ are owned by "root". That includes:

/var/svn/conf
/var/svn/db
/var/svn/hooks
/var/svn/locks

Do I need to create a ScriptStuff directory in /home/mydomain/domains/mydomain.com that's owned by user "mydomain" or is it just that that "mydomain" needs to be the owner of /var/svn/db?

*OR* am I missing the point of SVN entirely?

Regards,

Nate

[Stefan]

You should ask on the subversion users list for help since this is clearly a server setup problem.

And most TSVN users don't know CentOS...

http://subversion.apache.org/mailing-lists.html

[Naturally its a bogus name]

Makes sense. Thanks.

Nate

--
You received this message because you are subscribed to a topic in the Google Groups "TortoiseSVN" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tortoisesvn/Ir8XGypiIa0/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tortoisesvn...@googlegroups.com <mailto:tortoisesvn...@googlegroups.com> .
To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/a18b2c72-e6ce-4618-9f4b-c98d85937e8f%40googlegroups.com <https://groups.google.com/d/msgid/tortoisesvn/a18b2c72-e6ce-4618-9f4b-c98d85937e8f%40googlegroups.com?utm_medium=email&utm_source=footer> .
For more options, visit https://groups.google.com/d/optout.