Immediately after installation, Jenkins will allow anyone to run anything as user jenkins, which is bad. This page shows you how to set up basic security using the Configure Global Security page.
The Configure Global Security page has two sections in which you:
First, establish the user authentication method. For smaller, more informal installations, you can use Jenkins' own user database. For enterprise installations, you will want to use your corporate service, which allows users to log in to Jenkins with their usual username and password.
This is the simplest authentication scheme--Jenkins maintains its own independent user database. People can sign up for their own accounts, and you as the administrator decide who can do what in Jenkins.
If Jenkins is running on a Windows server then it is better to install the Active Directory plugin.
On a Linux host you have an option to either use the Active Directory plugin or an LDAP based authentication. To configure the LDAP to work with Active Directory, provide the following:
Note that the correct Manager DN value can vary greatly depending on your Active Directory set up.
To set up Network Information System:
See LDAP Plugin. Then continue with Authorization, below. In particular, do not forget to press the Save button at the bottom of the page.
The Authorization section of the Configure Global Security page allows you to configure what users are allowed to do once authenticated.
Matrix-based security offers the most precise control over user privileges.
If you set up a service like NIS, Active Directory or LDAP, you can now log in to Jenkins using your network credentials. If you are using Jenkins' own user database, create a user account for yourself:
If everything works smoothly, you are now logged on as yourself with full permissions. If something goes wrong, follow this to reset the security setting.
More docs to come. Suggestions on what needs to be written are greatly appreciated.
Skip to end of metadata Go to start of metadata