Rails 3.1 support about read_only_rubycas_server

[metasoarous]

I could be misunderstanding you, but it seems like you are a bit confused
about how the rubycas server works.

Rubycas Server is a Sinatra app (that happens to use ActiveRecord for ORM).
It handles authentication and then serves that authentication via the CAS
protocol (forget who outlined that) to any number of CAS clients. This
enables these clients to all have a single shared sign on, so that logging
into any one of the client applications logs you into all of them (useful if
you have a corporation with a bunch of web apps, each for different
purposes, or linked web apps of some sort that are best housed separately
but that you want shared authentication on).

The Rubycas server is standalone. It runs as an entirely separate
application from the clients. This decoupled nature is exactly what makes
CAS so awesome and useful (well, and possible, really). So if you want a
Rails 3.1 application to run off of the RubyCasServer services as a client,
then you need to be looking at the RubyCasClient gem. That is what you
would put in you rails 3.1 app in order to make it capable of consuming the
services.

My work was simply to enable someone to run a RubyCas Server on Heroku. It
has no implication whatsoever (at least in theory) with regards to what
clients consume those services. So you should be able to run it as is on
heroku (following the setup instuctions I lay out) and then install a
separate rails application as a client. Of course, if you only have one
client application (and don't expect to have more), then you should really
look at a different like authlogic or something.

I hope that I've been able to clarify things for you. If I am
misunderstanding you somehow, please let me know.

Chris

On Fri, Aug 5, 2011 at 10:05 PM, rlipman <
[email protected]>wrote:

I've been looking into deploying rails 3.1 app to heroku with
rubycas-server. I found your fork that works with heroku but it hasn't been
updated since 3.0. When I bundle install I get this error

Bundler could not find compatible versions for gem "activerecord":
 In Gemfile:
   rubycas-server depends on
     activerecord (~> 3.0.0)

   rails (= 3.1.0.rc4) depends on
     activerecord (3.1.0.rc4)

Reply to this email directly or view it on GitHub:
#1

[voidlily]

My bad, I completely read that wrong. I thought I needed to install
this as a gem inside my existing app, not deploy it as a separate app.

On Sat, Aug 6, 2011 at 2:17 AM, metasoarous
[email protected]
wrote:

I could be misunderstanding you, but it seems like you are a bit confused
about how the rubycas server works.

Rubycas Server is a Sinatra app (that happens to use ActiveRecord for ORM).
It handles authentication and then serves that authentication via the CAS
protocol (forget who outlined that) to any number of CAS clients. This
enables these clients to all have a single shared sign on, so that logging
into any one of the client applications logs you into all of them (useful if
you have a corporation with a bunch of web apps, each for different
purposes, or linked web apps of some sort that are best housed separately
but that you want shared authentication on).

The Rubycas server is standalone. It runs as an entirely separate
application from the clients. This decoupled nature is exactly what makes
CAS so awesome and useful (well, and possible, really). So if you want a
Rails 3.1 application to run off of the RubyCasServer services as a client,
then you need to be looking at the RubyCasClient gem. That is what you
would put in you rails 3.1 app in order to make it capable of consuming the
services.

My work was simply to enable someone to run a RubyCas Server on Heroku. It
has no implication whatsoever (at least in theory) with regards to what
clients consume those services. So you should be able to run it as is on
heroku (following the setup instuctions I lay out) and then install a
separate rails application as a client. Of course, if you only have one
client application (and don't expect to have more), then you should really
look at a different like authlogic or something.

I hope that I've been able to clarify things for you. If I am
misunderstanding you somehow, please let me know.

Chris

On Fri, Aug 5, 2011 at 10:05 PM, rlipman <
[email protected]>wrote:

I've been looking into deploying rails 3.1 app to heroku with
rubycas-server. I found your fork that works with heroku but it hasn't been
updated since 3.0. When I bundle install I get this error

Bundler could not find compatible versions for gem "activerecord":
 In Gemfile:
   rubycas-server depends on
     activerecord (~> 3.0.0)

   rails (= 3.1.0.rc4) depends on
     activerecord (3.1.0.rc4)

Reply to this email directly or view it on GitHub:
#1

Reply to this email directly or view it on GitHub:
#1 (comment)

[metasoarous]

No problem.

Do let me know though if you need to use the CAS Server on heroku, and if
so, how this fork goes for you.

Chris