| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2013-11-07 | only check number of disabled identities to make test more robust | Azul | |
| 2013-11-06 | use the account lifecycle from UsersController#destroy | Azul | |
| 2013-11-06 | integration test for blocking handles after account destroyed | Azul | |
| has not been run yet. | |||
| 2013-11-06 | refactor: extract method on account test | Azul | |
| also test one can't login anymore after destroying the account. | |||
| 2013-11-05 | Identity.destroy_all_disabled will clean up disabled identities | Azul | |
| This is mostly for cleaning up after tests so far. But we might expand this to destroy all identities disabled before a certain date. | |||
| 2013-11-05 | disabled identities to block handles after a user was deleted | Azul | |
| 2013-10-30 | test helper to expect_logout. | Azul | |
| Currently it expects both the session and the token to be cleared. This might change. But we'll always have a definition of what it means to logout we can test this way. | |||
| 2013-10-30 | notify user their account was successfully deleted (refs #4216) | Azul | |
| Also fixes a cornercase when admins deleted their own account. So far they would be redirected to the users list - which then refused access. Now they'll be redirected to the home landing page as well. | |||
| 2013-10-28 | no need to create a user for testing failed login attempt | Azul | |
| 2013-10-28 | reset button loading... state on error (#4231) | Azul | |
| including test refactored error display some | |||
| 2013-10-18 | test logging in through the API using python with umlauts | Azul | |
| 2013-10-17 | blacklist system logins for aliases and logins | Azul | |
| We blacklist based on three things: * blacklist in APP_CONFIG[:handle_blacklist] * emails in RFC 2142 * usernames in /etc/passwd The latter two can be allowed by explicitly whitelisting them in APP_CONFIG[:handle_whitelist]. We stick to blocking names that have been configured as both blacklisted and whitelisted - better be save than sorry. | |||
| 2013-09-26 | Since local part of email is case sensitive, want to allow remote email ↵ | jessib | |
| addresses with uppercase letters in local part. | |||
| 2013-09-25 | visual feedback when submitting forms (#3164) | Azul | |
| This also helps with the failing integration test. We needed a way to tell the ajax request was back. Observing the button state now works for that. | |||
| 2013-09-24 | use token auth when accessing the api from webapp | Azul | |
| One failing integration test still needs to be fixed | |||
| 2013-09-23 | This ensures that email addresses contain only lowercase letters, and that ↵ | jessib | |
| an identity's destination is a valid Email. | |||
| 2013-09-19 | Merge branch 'develop' into feature/only_lower_case_aliases | jessib | |
| 2013-09-19 | Merge pull request #82 from azul/feature/sessions-expire | jessib | |
| Feature/sessions expire | |||
| 2013-09-18 | user.account shortcut to Account.new(user) | Azul | |
| 2013-09-17 | integration tests for session expiry | Azul | |
| 2013-09-09 | Merge branch 'develop' into feature/only_lower_case_aliases | jessib | |
| 2013-09-05 | For moment, have identity's address handle aliased from login so we can use ↵ | jessib | |
| LoginFormatValidation. However, this is not how we will want it eventually. One issue is that the errors messages are set on login, rather than the appropriate field. | |||
| 2013-09-05 | Test of failing to add non-local email address as an identity's address. | jessib | |
| 2013-09-04 | use /login instead of /sessions/new and test successful login | Azul | |
| 2013-09-03 | Merge pull request #73 from azul/bugfix/3623-teardown-test-data-properly | jessib | |
| Bugfix/3623 teardown test data properly | |||
| 2013-09-03 | Merge pull request #75 from azul/feature/token-expiry | jessib | |
| Token expiry | |||
| 2013-09-03 | Merge pull request #76 from azul/feature/3600-visual-feedback-on-failed-signup | jessib | |
| Ensure json requests get json error response on failure | |||
| 2013-09-03 | Cleanup sessions controller - webapp logs in through the api. | Azul | |
| So the #create and #update actions were not needed anymore. Also removed the tests | |||
| 2013-09-03 | Account: Composition to handle User and its identities | Azul | |
| We have a lot of things that act upon a user record and one or more of it's identities at the same time: * Sing up: Create a user and it's initial identity * Rename: Change the username and create a new identity, turn old into an alias * Cancel Account: Remove user and all their identities. In order to keep the User and Identity behaviour isolated but still have a this logic represented in a sinle place the Account model deals with all these things. We could have overwritten the User#create, User#update and User#destroy methods instead. But then we would always create identities, even if we only need a user (for example in tests). | |||
| 2013-09-03 | cleanup records after running user integration tests | Azul | |
| 2013-09-03 | simplify users_controller_test | Azul | |
| 2013-09-03 | don't leave id records behind when unit testing | Azul | |
| 2013-09-03 | expire token according to config setting auth:token_expires_after | Azul | |
| 2013-09-03 | use Token#authenticate for authentication | Azul | |
| This will return the user. But we can add timestamp validations and updates here. | |||
| 2013-09-03 | integration test for displaying internal server error during signup | Azul | |
| 2013-08-30 | there's no need for User#find_by_param. clean it up | Azul | |
| 2013-08-27 | refactor: Changing the py test to use less globals and session only locally. | Azul | |
| 2013-08-27 | use token to update user password | Azul | |
| 2013-08-27 | separate different tests for showing non existant user | Azul | |
| This way the failed stubbing errors were more telling | |||
| 2013-08-27 | token.user will get you the right user | Azul | |
| 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. | |||
| 2013-08-27 | make sure find_record still works with real records | Azul | |
| 2013-08-27 | clear token on logout with test | Azul | |
| 2013-08-27 | basic testing for token based auth in tests | Azul | |
| 2013-08-27 | first steps towards enabling token based auth | Azul | |
| 2013-08-27 | minor: remove puts line | Azul | |
| 2013-08-22 | Merge pull request #69 from azul/bugfix/update_user_password_through_api | jessib | |
| Test updating user password through api | |||
| 2013-08-21 | use the same login validations on sessions and users | Azul | |
| The session ones were outdated so valid usernames could not login if they contained a '.' Refactored so both models use the same module for this validation to ensure consistency. | |||
| 2013-08-21 | also test updating the user password in python against dev.bm | Azul | |
| 2013-08-21 | integration test updating users password | Azul | |
| 2013-08-08 | Merge pull request #64 from azul/feature/identity-rewrite | jessib | |
| Feature/identity rewrite | |||
 |
index : leap_web.git | |
| [leap_web] | git repository hosting |
| summaryrefslogtreecommitdiff |