Closed bryanlarsen closed 12 years ago
Rails 3 uses the rubycas-client-rails gem instead of the Rails code in this gem, so a proper fix would be to move CasProxyCallbackController into rubycas-client-rails, but this should be a safe interim fix.
Makes sense
Rails 3 uses the rubycas-client-rails gem instead of the Rails code in this gem, so a proper fix would be to move CasProxyCallbackController into rubycas-client-rails, but this should be a safe interim fix.