summaryrefslogtreecommitdiff
path: root/users/config
AgeCommit message (Collapse)Author
2013-02-25Admins cannot update a user. Eventually we will want to allow admins to ↵jessib
update some user fields.
2013-02-25Add hint that password change is optionaljessib
2013-02-19Needs some cleanup, but this has one form where user can change username and ↵jessib
password (they can leave either the same if they just want to change one, but we should make this clearer.)
2013-01-29Allow PUT API to update user.jessib
2013-01-22Rough way to allow user to paste in their key, but certainly we will want ↵jessib
different display.
2013-01-22some basic webfinger routes, controller, presenters, viewsAzul
2013-01-17Merge pull request #16 from leapcode/feature/fixing-routes-with-apiazul
Fixing routes with api
2013-01-16using subdomain for api requests properlyAzul
2013-01-15Show different ticket characteristics when viewing the users versus when ↵jessib
listing the tickets. Give a message if a user has no tickets.
2013-01-15minor: put emails in unstyled ul and simplifyAzul
Just found out that render(@collection) returns nil for emtpy collections. So that is usefull for putting messages about the emtpy collection in an or clause.
2013-01-10moved api routes into their own namespaceAzul
In case we need them at some point - now it's new_api_user_path instead of new_user_path for example. This way they should not conflict with the normal route generation
2012-12-17enabled destroying email aliases - no ajax yet.Azul
2012-12-10actually allow adding email aliasesAzul
2012-12-09basic form added to user settings, simple model createdAzul
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-07adding a bunch of translationAzul
2012-11-26added admin menu and user index actionAzul
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-09seperated the warden classes from the initializerAzul
also commented the sessions controller test a bit and fixed it
2012-11-09got integration test and login flow to workAzul
2012-11-04Merge branch 'develop' into feature-warden-srpAzul
Conflicts: Gemfile.lock users/app/controllers/application_controller.rb users/leap_web_users.gemspec
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-17UI tweaks including newer version of bootstrapAzul
2012-10-11current_user and authenticate methodsAzul
2012-09-27added in leap web users - one repo to rule them allAzul