Thanks guys, I have got instances of ruby-cas and hancock both running
and like them both as solutions but I need to be able to run them on
top of my rails app. ie as rack midleware or something. So they can
talk to the same db on heroku.
Can I even do this?
I have tried, and they seem to be running but the routes to the sso
app are being ignored.
Looking for workarounds to not being able to point ruby-cas or hancock
to my main apps db to authenticate.
Cheers.
Sent from my iPhone
On 09/05/2010, at 3:04 PM, Nicholas Faiz <[email protected]>
wrote:
Yes, there's a rubycas-server & a rubycas-client (which is also a
Rails 2.x plugin).
It's a great project for SSO. You should have a look at it.
Nicholas
On May 9, 2:04 pm, Mikel Lindsaar <[email protected]> wrote:
There is a RubyCAS server that i have been playing with.
it is very complete from first brush.
Google RubyCAS
Mikel
On 7, May 2010, at 7 May 12:04, [email protected] wrote:
that looks cool james, thanks for the info..
its a CAS client though right?
Im looking for a CAS server.
I'll will however definitely give it a go in the apps that need to
authenticate against my main app.
On 7 May 2010 03:03, James A. Rosen <[email protected]> wrote:
You might take a look at my "Casrack the Authenticator" gem --
it's a
Rack middleware for authentication via CAS:http://rubygems.org/
gems/casrack_the_authenticator
I hope shameless self-promotion is permitted on this list :)
-James
On May 5, 5:46 pm, Luke Cunningham <[email protected]>
wrote:
Hey guys.
I'm wondering if any one has had experience with hancock or rubycas
for single sign on.
I have a rails app which uses authlogic for authentication, and I
want
to use it as the login point for a few services.
Will rubycas or hancock help me with that or is there an easier
way?
Everything will be running on heroku, and while I have managed to
get
instances of everything running obviously they can't point to my
main
apps database so Maybe they would have to run within my app? Rack/
metal?
Cheers
Luke
--
You received this message because you are subscribed to the
Google Groups "Ruby or Rails Oceania" group.
To post to this group, send email to rails-
[email protected].
To unsubscribe from this group, send email to [email protected]
.
For more options, visit this group athttp://groups.google.com/
group/rails-oceania?hl=en.
--
You received this message because you are subscribed to the Google
Groups "Ruby or Rails Oceania" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to [email protected]
.
For more options, visit this group athttp://groups.google.com/
group/rails-oceania?hl=en.
--
You received this message because you are subscribed to the Google
Groups "Ruby or Rails Oceania" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to [email protected]
.
For more options, visit this group athttp://groups.google.com/
group/rails-oceania?hl=en.
--
You received this message because you are subscribed to the Google
Groups "Ruby or Rails Oceania" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to [email protected]
.
For more options, visit this group athttp://groups.google.com/group/
rails-oceania?hl=en.
--
You received this message because you are subscribed to the Google
Groups "Ruby or Rails Oceania" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to [email protected]
.
For more options, visit this group at http://groups.google.com/group/rails-oceania?hl=en
.
--
You received this message because you are subscribed to the Google Groups "Ruby or
Rails Oceania" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/rails-oceania?hl=en.