sort authentication controller extension
first steps towards enabling token based auth
basic testing for token based auth in tests
clear token on logout with test
make sure find_record still works with real records
do not redirect if no token present

So far we allow two mechanisms of authentication:
  * session based
  * token based

If token fails session will be atempted in most cases. So we can't just redirect here or we get a double render error.
token.user will get you the right user

This way we can stub the token to return the user directly. Stubbing User.find_by_param is not a good idea as it will make all calls to User#find_by_param with a different id fail.
separate different tests for showing non existant user

This way the failed stubbing errors were more telling
use token to update user password
refactor: Changing the py test to use less globals and session only locally.
Merge pull request #72 from azul/feature/token-based-auth

Feature: Token based auth