My favorites | Sign in
Project Home Downloads Wiki Issues Source
Search
for
QuickStart  
Step-by-step installation and usage instructions
Featured, Phase-Deploy
Updated Aug 3, 2011 by matt.zuk...@gmail.com

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

Server Requirements

  • Ruby 1.8.7 or newer
    • It is possible to run under older versions of Ruby but it's not pretty.
  • 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 Unix-like OS such as Linux or Mac OS X (RubyCAS-Server should work on other platforms, but the instructions here are POSIX-specific)

Installation & Usage

  • RubyCAS-Server is now a Rack-based Sinatra app. Googling for general instructions on deploying a Sinatra app should get you most of the way there.
  • Install Bundler: gem install bundler
  • Download RubyCAS-Server through RubyGems: gem install rubycas-server
  • You'll need to copy the example config file under resources/config.example.yml to /etc/rubycas-server/config.yml.
  • Customize your config.yml file. You'll need to pick a database (e.g. MySQL, SQLite, etc.) and enable at least one authentication back-end.
  • Run rubycas-server.

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.

Running under Apache with Phusion Passenger

See DeployingUnderPhusionPassenger

Comment by xxdesmus, Apr 29, 2010

I see that you say "A Linux machine" ...what about a Unix environment? I'm hoping to set this up possibly on AIX or Solaris. Any words of wisdom for that environment?

Comment by project member matt.zuk...@gmail.com, May 31, 2010

I don't have access to an AIX or Solaris box, so can't say for sure, but I imagine RubyCAS should work fine there too.

Comment by oul...@gmail.com, Sep 18, 2010

gem version rubycas-server depends on activesupport and activerecord 2.1, but gem 1.3.6+ will install 3.0 instead. It's better to recommend when using gem to install them.

gem install -v=2.1 activesupport gem install -v=2.1 activerecord

Comment by hansheng...@gmail.com, Dec 29, 2010

Hey, I have installed RubyCAS on Windows. It's great. Just make sure if you are using IIS, change the port of the config.yml to say port: 900

That way, you will not have conflict with IIS 443 ports.

There's a problem using space as a password. I got test account in AD using space. Wonder why it doesn't go thru!

Comment by takacs.z...@gmail.com, Jan 13, 2011

I think I found a bug in the new install. When I try to run "rake db:migrate", rspec/core/rake_task is missing.

You put the code in block-comments. However, it doesn't work in a rakefile. I used #-s on spec.rake line-beginnings.

The second thing is: I have mysql installed, so I had to use mysql2 gem, and change adapter type to "mysql2".


Sign in to add a comment
Powered by Google Project Hosting