Skip to content

upgraded from 2.3.3-3.1 to 2.8.7 / using multiple useAuthenticationFile-directives does not work anymore #235

Description

@Starfish4711git

Hi,

I hope this is the right place to ask this this question, but I did not find any other.

We have been using WebSVN up to version 2.3.3 for years and now we had to upgrade to a more current version, because of PHP7 being deprecated.

We are using 3 local parent directories wherein the repositories are placed, accordingly there are 3 parentpath-directives within our config.php file, like this:
$config->parentPath('/data1/svn/repobase/xxx/data', 'groupx');
$config->parentPath('/data1/svn/repobase/yyy/data', 'groupy');
$config->parentPath('/data1/svn/repobase/zzz/data', 'groupz');

Each of this parent directories is using its own svnauthz.conf file, therefor we had lines like these:
$config->useAuthenticationFile('/data1/svn/repobase/xxx/permissions/svnauthz.conf');
$config->useAuthenticationFile('/data1/svn/repobase/yyy/permissions/svnauthz.conf');
$config->useAuthenticationFile('/data1/svn/repobase/zzz/permissions/svnauthz.conf');

First of all I noticed that naming has been changed in the meantime and I had to replace "useAuthenticationFile" with "useAccessFile".

Now configuration is accepted, but WebSVN does not show all 3 repo bases anymore, but only the one of the latest "useAuthenticationFile" directive. If I change the order or comment out later directives, the last active directive "wins".

How do I get back the original behavior? Is there some additional configuration I have to adjust, is it a bug, is it intended that way?

Thanks in advance!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions