All user management tasks are handled by OpenLDAP. The phpLDAPadmin web client is installed ot provide easy access to create users and assign them to groups. All other systems on the server use the information in OpenLDAP to make authentication and authorization decisions.
The defualt configuration assumes all SVN repositories will be immediately below the /var/svn directory. Any SVN repository created here will automatically be available via WebDAV through Apache, and will also show up in the WebSVN interface.
To receive email notifications when SVN checkins occur, the SVN::Notify tool has been installed on the system. Look at the /var/svn/example/hooks/post-commit script for an example about how to enable the tool on a per repository basis.
Anyone in the svn-commiters group in OpenLDAP will be able to make changes to any repository on the system. All users (including anonymous users) have read access to all repositories by default.
By default, any user that can be authenticated via OpenLDAP will have access to Jenkins.
Only users in the jenkins-administrators group in OpenLDAP will be granted admin rights in Jenkins though.
By default, there are no security checks for read access to any of the repositories available through Nexus.
By default, only users in the nexus-administrators group in OpenLDAP will be granted admin rights.
To be able to deploy new artifacts (to the hosted snapshot and release repositories for example) a user must be a member of the nexus-deployers group in OpenLDAP.
Need help with your Adobe CQ 5.4 and 5.5 implementation? We're here to help. Contact us at info@headwire.com
Jumpstart your CQ project - consider the twitter bootstrap implementation with CQ providing a wysiwyg template editor and base components for an every day website.