Given a public project And a platform backed by LDAP And a platform that has restricted users And a project that opted-out of LDAP for SVN Then, Tuleap 15.2 generates the following SVN permissions

[/]
* = r 
@members = rw

While 15.2.99.181 does:

[/]
* = 
@members = rw

It's likely to be a side effect of git #tuleap/stable/1182b1ef816e9aa2b9d33ffa91be270196ba749d

Additional Context

1. On Tuleap 15.2 and before: the check for restricted users was in LDAP plugin
2. With the refactoring [0], the check for restricted users is moved to core and always applies, regardless of LDAP
3. To fix this request, the check for restricted users should be moved back to LDAP plugin (to match the previous behaviour)

So, when a repository is controlled by LDAP and its project is public, there should be an additional check for restricted users; when restricted users are allowed, repo is not readable (* =); when no restricted users, repo is readable (* = r)

The production issue is that with the refactoring, an SVN repo that is not controlled by LDAP, in a public project, on a platform with restricted is not readable (* =) but it should be readable (* = r).

[0] git #tuleap/stable/1182b1ef816e9aa2b9d33ffa91be270196ba749d