Jump to: navigation, search

Hudson-ci/Using Hudson/Securing Hudson

This article is a stub. It will be expanded as content is migrated from the Hudson-CIWeb site.

In the default configuration, Hudson does not perform any security check. This means any person accessing the website can configure Hudson and jobs, and perform builds. While this configuration is normally acceptable for intranet use, Hudson can be also configured to authenticate users and enforce access control so that it can be exposed to the untrusted environment, such as the internet.

This setting is controlled mainly by two axes:

Security Realm, which determines users and their passwords, as well as what groups the users belong to.
Authorization Strategy, which determines who has access to what.

These two axes are orthogonal, and need to be individually configured. For example, you might choose to use external LDAP or Active Directory as the security realm, and you might choose "everyone full access once logged in" mode for authorization strategy. Or you might choose to let Hudson run its own user database, and perform access control based on the permission/user matrix.


Quick and Simple Security — if you are running Hudson like "java -jar hudson.war" and only need a very simple set up
Standard Security Setup — discusses the most common set up of letting Hudson run its own user database and do finer-grained access control
Apache frontend for security — run Hudson behind Apache and perform access control in Apache instead of Hudson
Authenticating scripted clients — if you need to programatically access security-enabled Hudson web UI, use BASIC auth
Help! I locked myself out! — if something goes really wrong and you can't get full access anymore

Security Implication

Note that even when security is enabled, builds that are performed in Hudson still retains the full access to the entire system, because they run as different processes. This implies any committor to any of the projects built in Hudson has full access to the system. They can change the build script to look at any files in the system that Hudson has access to, and modify them.

Also, if you are using the master/slave mode, slaves that are connected to Hudson also gains the full access to the entire Hudson build cluster, since a slave can send code to the master to be executed.

On the other hand, Hudson does not escape any input strings. You can use any HTML tags and also someone can embed harmful scripts. Appropriate security settings must be required.