Commit graph

15 commits

Author SHA1 Message Date
Reinier Balt
4d46750f05 fix #1167 2011-05-08 15:03:55 +02:00
Reinier Balt
f0ec5647d4 migrate user js 2011-02-03 18:19:30 +01:00
Reinier Balt
a02f1d2584 migrate dependencies
without functional changes
2011-02-03 18:19:29 +01:00
Stefan Richter
1c90b90909 fixing some stuff around OpenID:
- adding missing Javascript includes
	- fixing jquery for showing/hiding indentity url field
	- adding identity url field to signup form
	- fixing bug in signup controller
2011-01-24 16:14:56 +08:00
Marcus Ilgner
338d4bb5a6 Added locale selection to preferences
Mostly completed transition to full i18n
Incorporated german translations by Ulf Klose <ulf.klose@gmail.com>
2011-01-16 18:14:07 +01:00
Marcus Ilgner
fd3f69d927 Changed code to support basic i18n.
Added RubyMine configuration and rvm setup to .gitignore.
2010-11-09 16:31:26 +08:00
Eric Allen
b87f4cc12e Revert i18n changes
We haven't merged that branch yet to trunk
2010-01-12 17:49:39 -08:00
Erik Ordway
901af95c69 clean up debug code and get new user correct 2010-01-12 17:18:01 -08:00
Erik Ordway
5b431ef50a This allows CAS to work side by side with other Auth methods.
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.
2010-01-12 17:17:56 -08:00
Erik Ordway
aaf3965004 use correct value 2009-12-18 09:42:05 -05:00
Erik Ordway
f259924a85 when CAS is switched app functions as normal but does not use any other auth methods. 2009-12-18 09:42:05 -05:00
Erik Ordway
b85b3fc081 allow adding users and set new users has having cas as the auth type 2009-12-18 09:40:12 -05:00
Reinier Balt
d931d4b627 fixes #919 for managing usernames with "." in it. Thanks Crea 2009-06-30 12:12:21 +02:00
MHarris
ed76cf55d2 Changed UsersController#index to use will_paginate plugin instead of classic_pagination
Made corresponding change in view.
Added User.per_page method to provide number of users per page to User.paginate button.  I can remove and just pass the param to the method in the controller if that is more desirable.
Added 2 controller tests for pagination.  No view tests have been added.
2008-07-14 13:10:55 -04:00
bsag
4cbf5a34d3 Removed superfluous 'tracks' directory at the root of the repository.
Testing commits to github.
2008-05-20 21:28:26 +01:00