stable

Clone or download

Read-only

Check restricted access in SVN

Given the platform allows restricted users And you have a project in "Private" access (without restricted) And a restricted user is still member of the project And restricted is still present in the .SVNAccessFile [groups] definition, When another user is added to the project And corresponding system event is done, Then .SVNAccessFile definition is updated to remove restricted user from project member And svn commit from restricted users are rejected. Same behavior when project switch from 'Private incl. restricted' to 'Private' (restricted are removed from svn access file) or when project switch from 'Private' to 'Private incl. restricted' (restricted are added back to svn access file). Same behavior when ldap is used for svn authentication for the project. Note: Tuleap.pm must be redeployed and caches invalidated Some BackendSVN tests have been moved to phpunit. Part of story #12554: have private projects without restricted members Change-Id: I6db7b59a5737ce17696466b63130596849bb9e24

Modified Files

Name
M plugins/ldap/include/LDAP_BackendSVN.class.php +48 −36 Go to diff View file
M plugins/ldap/include/LDAP_UserDao.class.php +28 −22 Go to diff View file
M plugins/svn/include/svnPlugin.class.php +10 −0 Go to diff View file
M src/common/backend/BackendSVN.class.php +55 −43 Go to diff View file
M src/common/dao/ProjectDao.class.php +15 −4 Go to diff View file
M src/utils/svn/Tuleap.pm +2 −2 Go to diff View file
A tests/phpunit/common/Backend/BackendSVNTest.php +146 −0 Go to diff View file
M tests/simpletest/common/backend/BackendSVNTest.php +0 −85 Go to diff View file