This is at least one issue with this
to logout of CAS you need session information but the logout method blows this away so I do the cas log out before the session is killed so the session persistest in rails. Because I needed to move the CAS before filters into login_cas and out of the application to make it work side by side. The user will still be logined into tracks even though their CAS session is closed as the session will still be there.
def logout
@user.forget_me if logged_in?
cookies.delete :auth_token
session['user_id'] = nil
if ( SITE_CONFIG['authentication_schemes'].include? 'cas') && session[:cas_user]
CASClient::Frameworks::Rails::Filter.logout(self)
else
reset_session
notify :notice, "You have been logged out of Tracks."
redirect_to_login
end
end
The other issue I have with this is that:
I could not find a use case for having mixed auth when using CAS. The reason to move to CAS is that all your users use CAS all the time. Even for admin accounts. Moodle is a good example of this in that when you activate CAS the default is that you can now only access moodle via CAS. By allowing mixed auth and self signup you end up with a anyone (the public) being able to sign up for accounts.
Still lacks error checking for circular dependencies and other validation.
Also, javascript for displaying the new item is broken.
Conflicts:
app/views/layouts/standard.html.erb
Pending state is displayed in the date_span. Successor information is displayed in the tooltip of a successor icon placed after the action description.
Conflicts:
app/helpers/todos_helper.rb
public/javascripts/application.js
The database contains actions with dependencies.
Please rename to tracks-17-blank.db or update database path accordingly.
Conflicts:
app/views/todos/toggle_check.js.rjs
Translating from strftime format to jQuery UI's format on the fly on every
page render. That kind of sucks, but it works. I think I have enough
translations here to cover everybody, but possibly not.
Caught a couple of things that I had to fix plus a handful of broken tests. This is the first time in forever that we have a fully successful selenium suite.
