Skip to main content

Public

Project privacy set to public. By default, its content is available to everyone (authenticated or not). Please note that more restrictive permissions might exist on some items.

    •  
      request #8752 Default svn permissions for public project are not valid
    Actions
    Infos
    #8752
    Manuel Vacelet (vaceletm)
    2016-01-06 12:04
    2016-01-06 10:38
    8869
    Details
    Default svn permissions for public project are not valid
    On c6.valid "mv-valid-8-9-frs" project, defined as public, I have the following svn permissions:
    [/]
    * =
    @members = rw

    Whereas it should be
    [/]
    * = r
    @members = rw
    SCM/Subversion
    development
    Empty
    • [ ] enhancement
    • [ ] internal improvement
    Empty
    Stage
    Thomas Gerbet (tgerbet)
    Declined
    2016-01-06
    Attachments
    Empty
    References
    References list is empty
    Display settings

    Follow-ups

    User avatar
    Thomas Gerbet (tgerbet)2016-01-06 12:04
    It appears this is the wanted comportment when you use the SVN LDAP backend.

    When the restricted users are enabled on the platform, a SVN repo should not possible to everyone even with a public project. When the LDAP backend is used, it is not possible to check if a member is restricted or not. The default permissions only allow access to project members in that case.
    • Status changed from New to Declined
    • Close date set to 2016-01-06