[jira] [Updated] (SVN-4865) "[/] @group = rw" not working after upgrade to SVN 1.13

["Daniel Shahaf (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SVN-4865?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Daniel Shahaf updated SVN-4865:
-------------------------------
    Component/s:     (was: mod_authz_svn)
                 libsvn_repos

> "[/] @group = rw" not working after upgrade to SVN 1.13
> -------------------------------------------------------
>
>                 Key: SVN-4865
>                 URL: https://issues.apache.org/jira/browse/SVN-4865
>             Project: Subversion
>          Issue Type: Bug
>          Components: libsvn_repos
>    Affects Versions: 1.13.0
>         Environment: Ubuntu 20.04.1 LTS
>            Reporter: Lorenz Froihofer
>            Priority: Major
>
> After upgrading Ubuntu from 18.04 to 20.04, which includes the upgrade of Subversion from 1.9 to 1.13, the following setup no longer works, but according to the docs, the [/] approach should still be working.
> Example illustrating the bug - no access for group "unlimited" to repository "repo1":
> {noformat}
> [groups]
> unlimited = user1, user2
> [/]
> @unlimited = rw
> [repo1:/]
> user3 = rw{noformat}
> In this example, user1 and user2 do not have access to repo1. This was working in SVN 1.9 and I could not find anything in the docs that this would have been removed on the way to 1.13.
> If I change the line "@unlimited = rw" to "* = r", then all users get read access as documented, meaning that the [/] definition is still applied to all repository-specific definitions.
> The @unlimited group gets access to repo1 if I add that group explicitly to the [repo1:/] section. However, this is only a workaround and requires quite some effort if you have a high number of repositories.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)