This document describes how to configure Rundeck for SSL/HTTPS support, and assumes you are using the rundeck-launcher standalone launcher. If you are using RPM/deb install, refer to the appropriate configuration file paths from Configuration -> Configuration Layout.

  1. Before beginning, do a first-run of the launcher, as it will create the base directory for Rundeck and generate configuration files.

    cd $RDECK_BASE;  java -jar rundeck-launcher-1.1.0.jar

    This will start the server and generate necessary config files. Press control-c to shut down the server.

  2. Using the keytool command, generate a keystore for use as the server cert and client truststore. Specify passwords for key and keystore:

    keytool -keystore etc/keystore -alias rundeck -genkey -keyalg RSA -keypass admin -storepass admin

    Be sure to specify the correct hostname of the server as the response to the question "What is your first and last name?". Answer "yes" to the final question.

    You can pass all the answers to the tool on the command-line by using a HERE document.

    Replace the first line "Venkman.local" with the hostname for your server, and use any other organizational values you like:

        keytool -keystore etc/keystore -alias rundeck -genkey -keyalg RSA -keypass adminadmin -storepass adminadmin  <<!
        My org
        my city
        my state
  3. CLI tools that communicate to the Rundeck server need to trust the SSL certificate provided by the server. They are preconfigured to look for a truststore at the location: $RDECK_BASE/etc/truststore. Copy the keystore as the truststore for CLI tools:

    cp etc/keystore etc/truststore
  4. Modify the file to specify the location of the keystore and the appropriate passwords:

    vi server/config/

    An example file (from the RPM package).

  5. Configure client properties. Modify the file $RDECK_BASE/etc/ and change these properties:

    • framework.server.url
    • framework.rundeck.url
    • framework.server.port

    Set them to the appropriate https protocol, and change the port to 4443, or to the value of your -Dserver.https.port runtime configuration property.

  6. Configure server URL so that Rundeck knows its external address. Modify the file $RDECK_BASE/server/config/ and change the grails.serverURL:

    • grails.serverURL=https://myhostname:4443

    Set the URL to include the appropriate https protocol, and change the port to 4443, or to the value of your -Dserver.https.port runtime configuration property.

  7. For Debian/RPM installation, uncomment line 43 in /etc/rundeck/profile:

    export RDECK_JVM="$RDECK_JVM -Drundeck.ssl.config=/etc/rundeck/ssl/ -Dserver.https.port=${RDECK_HTTPS_PORT}"
  8. Start the server. For the rundeck launcher, tell it where to read the

    java -Drundeck.ssl.config=$RDECK_BASE/server/config/ -jar rundeck-launcher-1.1.0.jar

    You can change port by adding -Dserver.https.port:

        java -Drundeck.ssl.config=$RDECK_BASE/server/config/ -Dserver.https.port=1234 rundeck-launcher-1.1.0.jar

    If successful, you will see a line indicating the SSl connector has started:

    Started SslSocketConnector@

Securing passwords

Passwords do not have to be stored in the ssl.config. If they are not set, then the server will prompt on the console for a user to enter the passwords.

If you want the server to start without prompting then you need to set the passwords in the config file.

The passwords stored in can be obfuscated so they are not in plaintext:

Run the jetty "Password" utility:

$ java -cp server/lib/jetty-6.1.21.jar:server/lib/jetty-util-6.1.21.jar <password>

This will produce two lines, one starting with "OBF:"

Use the entire OBF: output as the password in the file, eg:


Troubleshooting keystore

Some common error messages and causes: Keystore was tampered with, or password was incorrect

A password specified in the file was incorrect.

2010-12-02 10:07:29.958::WARN: failed SslSocketConnector@ /Users/greg/rundeck/etc/keystore (No such file or directory)

The keystore/truststore file specified in doesn't exist

Optional PEM export

You can export the PEM formatted server certificate for use by HTTPS clients (web browsers or e.g. curl).

Export pem cacert for use by e.g. curl:

keytool -export -keystore etc/keystore -rfc -alias rundeck > rundeck.server.pem

Using an SSL Terminated Proxy

You can tell Jetty to honor X-Forwarded-Proto, X-Forwarded-Host, X-Forwarded-Server and X-Forwarded-For headers by adding the following JVM property:

  • rundeck.jetty.connector.forwarded set to "true" to enable proxy forwarded support.

E.g. modify the RDECK_JVM variable in the file /etc/rundeck/profile and add:


This will enable Jetty to respond correctly when a forwarded request is first received.

Note: You will still need to modify the grails.serverURL value in to let Rundeck know how to properly generate absolute URLs.

Disabling SSL Protocols

You can disable SSL protocols using this JVM variable:

  • rundeck.jetty.connector.ssl.excludedProtocols set to a comma-separated list of SSL protocols to disable.

If unset, the default value of 'SSLv3' will be used.

E.g. modify the RDECK_JVM variable in the file /etc/rundeck/profile and add:


When starting up the Jetty container will log a list of the disabled protocols:

2014-10-27 11:08:41.225:INFO:oejus.SslContextFactory:Enabled Protocols [SSLv2Hello, TLSv1] of [SSLv2Hello, SSLv3, TLSv1]