We have our own internal single sign on system that is basically modeled
after Yale''s CAS and is written in perl/mod perl. It uses kerberos and
implements the basic CAS protocol (no proxy support). I''m in the
process of
writing the rails code for the client side and was looking at the
possibility of writing the server side in ruby/rails also. But since ruby
doesn''t have any kerberos bindings I''m left wondering what a
good
alternative to kerberos would be. Ldap comes to mind, but I doubt most
people would want to use it if it required ldap, and I will probably release
this as open source, assuming I actually go ahead with it.
Any thoughts on what a good alternative authentication source could be?
Something secure but also fairly easy to install and configure?
I did think of using swig to create some ruby bindings, but I''m just
not
familiar enough with kerberos to take that on at the moment.
Chris
_______________________________________________
Rails mailing list
Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
http://lists.rubyonrails.org/mailman/listinfo/rails