Overview

To set up a full CAS infrastructure you will have to:

1. Install the CAS server for your organization (i.e. install RubyCAS-Server, although other implementations exist, such as JA-SIG CAS)
2. Configure the CAS server's method for validating usernames and passwords. Out of the, box RubyCAS-Server can authenticate against an LDAP directory, a SQL database, Microsoft's Active Directory, etc. It is also possible to write a custom authenticator with a little bit of Ruby coding.
3. Add CAS clients to your web applications. CAS clients are available for most major web frameworks, including Java, PHP, and Ruby on Rails.

Installation

Requirements

• Ruby 1.8.4 or newer
• RubyGems
• Ruby bindings for your preferred database. MySQL will probably work out-of-the-box. For other databases like SQLite3 and PostgreSQL you may have to install additional Ruby libraries first (e.g. gem install sqlite3-ruby for SQLite3).
• An SSL certificate (CAS requires SSL)
• A Linux machine (RubyCAS-Server should work on other platforms, but currently has only been tested under Linux)

Installation & Usage

1. Make sure you have all of the requirements listed above.
2. Install RubyCAS-Server: gem install rubycas-server (you must be root to do this, so try it with sudo). This will install the package from rubyforge.org, along with the necessary dependencies (picnic, activesupport, activerecord, etc.). If you are installing locally via a manually downloaded gem file, you will have to get the dependencies yourself, so the default method of installing it via rubyforge is strongly recommended.
3. Run /usr/bin/rubycas-server. you should get an error message about a missing configuration file; a sample config will be created for you at /etc/rubycas-server/config.yml.
4. Edit the sample configuration to match your needs. The file is well documented, so you should be able to figure it out.
• If you don't have an SSL certificate yet, you can download a sample certificate for testing purposes here.
• Be sure to uncomment one of the 'authenticator' configurations.
• Be careful about indentation. Use only spaces, not tabs! The configuration uses YAML, which is very sensitive to indentation.
5. Run /usr/bin/rubycas-server (try /usr/bin/rubycas-server -h for a list of command-line options).

You should now be up and running. Depending on the settings you entered in your config.yml file (i.e. port, hostname, etc.), the server should now be available at https://localhost (or some variation thereof).

More detailed configuration information is available at HowToConfigure and UsageScenarios, but if you prefer to jump right in, you should be able to figure things out based on the comments in the sample config.

If you encounter any bugs or issues with RubyCAS-Server, please do not hesitate to open an issue ticket!

You can also ask for help via the RubyCAS Google Group.

Installing as an init.d service

Optionally, you can set up RubyCAS-Server to run as a background service on your linux server using the init.d mechanism:

1. In the resources subdirectory of the RubyCAS-Server distribution, you'll find an init.d.sh script. Rename this to /etc/init.d/rubcas-server. (If you installed RubyCAS-Server as a gem, you should find this in something like /usr/lib/ruby/gems/1.8/gems/rubycas-server-0.4.0/resources/init.d.sh).
2. Add the rubycas-server script to startup. This should be something like chkconfig -a rubycas-server (on Debian/Ubuntu, it will probably be update-rc.d rubycas-server defaults).

The init.d script simply uses the rubycas-server-ctl script to start and launch the server. If you wish, you can do this manually; rubycas-server-ctl start starts the server, and rubycas-server-ctl stop stops it. If you run into trouble with the init.d script, try manually running rubycas-server-ctl start --verbose and you should get a detailed explanation of the problem.

Running under Apache with Phusion Passenger

See DeployingUnderPhusionPassenger