GoCD was built from the bottom up with security in mind. GoCD server provides both an http service and an https service by default. The http service listens on port 8153 and the https service listens on port 8154.
Support for in-built Password-File based and LDAP authentication has been disabled. Alternatively, GoCD provides extensions through Authorization Endpoints using which plugins can provide authentication and authorization services backed by any authorization service providers like LDAP, Google, Github etc.
By default, GoCD does not require users to authenticate. However, users can be forced to authenticate by installing and configuring any of the Authorization plugins. GoCD comes bundled with a Password File based and LDAP/AD authentication plugins.
You should be able to configure any number of Authorization plugins, GoCD would attempt authenticating the user with each plugin (in no specific order) until a successful authentication.
GoCD forces a perodic re-authentication of users, this is to ensure any changes like removing of users or roles in the external authorization server are reflected in GoCD. The re-authentication interval is controlled by the system property
go.security.reauthentication.interval which is defaulted to 30 minutes. The plugins could potentially be written in a way to detect such changes in the external system, and notify GoCD server to force a reauthentication of users.
You could use one or more of the below to tweak the session config:
|System property name||Default value||Description|
||Idle session timeout (in seconds). Do not set this to
||Expiry of a session cookie. Set to
||Set this to
GoCD checks if an authenticated user is an existing user or a new user (logging in for the first time). For new users, there are two behaviors GoCD can operate under:
- Automatically register the new user in GoCD and continue with the login process.
- Deny access to the user if not already a registered GoCD user. New users will have to be explicitly added by an admin.
To switch the mode in which the GoCD Server operates:
- Login to GoCD as an admin
- Navigate to the "Admin" section
- Click on the "Server Configuration" tab
- Set the "Allow users that exist in LDAP, password file or via plugin to log into GoCD, even if they haven't been explicitly added to GoCD." checkbox