summaryrefslogtreecommitdiff
path: root/users/app/controllers
AgeCommit message (Collapse)Author
2012-12-17activate email tab after changing email settingsAzul
2012-12-17enabled destroying email aliases - no ajax yet.Azul
2012-12-17Merge branch 'feature/fixing-signup-and-login-issues'Azul
2012-12-13Merge branch 'master' into developAzul
Conflicts: users/test/unit/user_test.rb
2012-12-12Merge branch 'master' into developAzul
2012-12-11make sure can login twiceAzul
2012-12-10email format validationsAzul
2012-12-10actually allow adding email aliasesAzul
2012-12-09basic form added to user settings, simple model createdAzul
2012-12-09first steps towards email aliasesAzul
* unit tests draft * controller draft
2012-12-08serve api version 1 in /1/Azul
Just a very simple start for now. Do we want to use the api for the secure remote password auth from js?
2012-12-07Merge branch 'master' into help_developjessib
Conflicts: app/views/layouts/application.html.haml help/app/controllers/tickets_controller.rb help/test/functional/tickets_controller_test.rb users/test/support/stub_record_helper.rb
2012-12-07fixed signup and removed flash that was not getting displayedAzul
I also tried flash.keep(:notice) but that did not help - not sure how to keep the flash until the root url has rendered.
2012-12-07first stub at displaying success messagesAzul
2012-12-07using normal requests for user updates except passwordAzul
password requires ajax for secure remote password to work
2012-12-03enable users to cancel their accountAzul
2012-12-01Merge branch 'develop' into help_developAzul
2012-11-28admins can destroy usersAzul
I changed the permissions a little to be more consistent. Now: * admins can edit users * users can destroy themselves. There's no ui for either of them but theoretically they could. Not sure this is what we want though.
2012-11-26Merge branch 'develop' into help_developjessib
2012-11-26Merge branch 'develop' into help_developjessib
Conflicts: users/app/views/sessions/_nav.html.haml
2012-11-26basic typeahead and user querying workingAzul
2012-11-26basic users index with typeahead searchAzul
2012-11-26added admin menu and user index actionAzul
2012-11-26simplified controller and adjusted testsAzul
Also added #assert_json_error to tests.
2012-11-23identify user by id so rerendering the form does not use new invalid loginAzul
2012-11-23test editing user settingsAzul
2012-11-22basic user edit form and actionsAzul
2012-11-22beautify login workflowAzul
* translating error messages * not caching login and password in js anymore * catching non responses
2012-11-22using client side validations for loginAzul
2012-11-22using the new srp.js apiAzul
2012-11-12Merge branch 'develop' into help_developjessib
Conflicts: help/test/functional/tickets_controller_test.rb users/test/functional/application_controller_test.rb users/test/support/auth_test_helper.rb
2012-11-09got integration test and login flow to workAzul
2012-11-06first steps towards warden srp testingAzul
2012-11-05Unit test for is_admin?jessib
2012-11-05Use the same URL for viewing tickets when authenticated or not---the couchdb ↵jessib
ID will be the random string for the secret URL. Tickets created when user was unauthenticated will be viewable by anybody who knows the URL.
2012-11-04fixed functional testsAzul
2012-11-04stubbing current_user the warden wayAzul
2012-11-04Merge branch 'develop' into feature-warden-srpAzul
Conflicts: Gemfile.lock users/app/controllers/application_controller.rb users/leap_web_users.gemspec
2012-11-02Some rough functionality for tickets, like showing ticket list for admins, ↵jessib
and initial way to close tickets.
2012-10-31Code to check administration (and ugly test display.) This includes example ↵jessib
config file.
2012-10-31using controller extensions for application controller by handAzul
2012-10-30sending proper error messages from warden.Azul
still need to translate these
2012-10-30using rails_warden bit of refactoringAzul
without rails_warden the failure app action was not getting set properly.
2012-10-30adding in warden with a basic strategyAzul
currently failing because we are not setting the content-type header.
2012-10-11current_user and authenticate methodsAzul
2012-10-11use ruby-srp 0.1.3 which returns the user on authenticate callAzul
Also removed a few hooks to User.current. Will replace with current_user
2012-10-05ruby-srp 0.1.1 has to_json method - simplifies controllerAzul
2012-10-05moving to ruby_srp 0.1.0, works with python srpAzul
2012-10-05Merge remote-tracking branch 'origin/master' into developAzul
Conflicts: users/app/controllers/sessions_controller.rb
2012-10-02Some more tweaks to help ticket models. Still want to tweak current_user ↵jessib
access from users engine.