Age | Commit message (Collapse) | Author | |
---|---|---|---|
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 | do not redirect if no token present | Azul | |
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. | |||
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 | sort authentication controller extension | Azul | |
2013-08-27 | minor: remove puts line | Azul | |
2013-08-26 | add public/img and config/couchdb.yml.* to gitignore | Azul | |
[ci skip] | |||
2013-08-22 | Merge pull request #69 from azul/bugfix/update_user_password_through_api | jessib | |
Test updating user password through api | |||
2013-08-22 | Merge pull request #70 from azul/bugfix/validate_login_like_signup | jessib | |
use the same login validations on sessions and users | |||
2013-08-21 | Merge remote-tracking branch 'jessib/js_warning' | Azul | |
2013-08-21 | return 204 NO CONTENT on API logout | Azul | |
That's the only meaningful response. | |||
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-20 | Tweak to parameters to fix wrong-number-of-arguments error blocking other work. | jessib | |
2013-08-19 | Change JS warning message per https://leap.se/code/issues/3492 | jessib | |
Key must end in _html so the html doesn't get escaped. | |||
2013-08-15 | Merge pull request #66 from jessib/feature/comment_creation_access | azul | |
Per ISEC informational issue, manually set the private property only in ... | |||
2013-08-13 | Fix this, so the comment will get set to false in cases where the user isn't ↵ | jessib | |
an admin. | |||
2013-08-12 | Per ISEC informational issue, manually set the private property only in ↵ | jessib | |
cases where it is an admin who set it. | |||
2013-08-08 | Merge pull request #64 from azul/feature/identity-rewrite | jessib | |
Feature/identity rewrite | |||
2013-08-08 | Merge branch 'bugfix/3410-close-srp-vulnerablility' | Azul | |
2013-08-08 | close srp vulnerability and report error in webapp | Azul | |
2013-08-07 | integration test exploiting srp vulnerability | Azul | |
2013-07-31 | added empty 'home' layout and removed debugger from homecontroller | elijah | |
2013-07-24 | also destroy the identity for a test user during teardown | Azul | |
2013-07-24 | keeping the pgp_key accessors for User so views still work | Azul | |
2013-07-24 | separate signup and settings service objects for user | Azul | |
2013-07-24 | removed email settings controller and views | Azul | |
PGP setting has been moved into account settings. It's using the API now issueing an Ajax request without any visual feedback. This obviously is not what we want but it hopefully suffices for uploading gpg keys for testing purposes before the Identity UI is in place. | |||
2013-07-24 | setter for keys for dirty tracking, more robust tests | Azul | |
Just altering identity.keys did not mark identities as changed. Also we now have a sane default for keys. | |||
2013-07-24 | test user validates uniqueness of login amongst aliases | Azul | |
2013-07-24 | no need for a remote email class | Azul | |
2013-07-24 | support deprecated API to set users main identity pgp key | Azul | |
We'll want to get rid of the #public_key and #public_key= functions but they are still used from the users controller. We'll probably have an identity controller instead at some point. | |||
2013-07-24 | remove email aliases test - we'll move them to identities | Azul | |
2013-07-24 | add keys to identity | Azul | |
2013-07-24 | remove the remainders of email aliases and forward from user | Azul | |
2013-07-24 | allow available and unique forwards only | Azul | |
2013-07-24 | validations of email format and local domain moved over | Azul | |
2013-07-24 | local email adds domain if needed | Azul | |
2013-07-24 | testing all versions of emial identities, emails are now strings | Azul | |
2013-07-24 | move identity creation into user class | Azul | |
It's always based on a user and most default values are based on user properties. | |||
2013-07-24 | first take on identity model - still broken | Azul | |
2013-07-17 | Merge pull request #63 from azul/bugfix/3201-fix-empty-config-error | azul | |
Fix breakage due to empty config file for a given env | |||
2013-07-17 | Fix breakage due to empty config file for a given env | Azul | |
2013-07-16 | Merge pull request #60 from azul/bugfix/srp-fix-for-zeroprefixed-hashes | jessib | |
Bugfix/srp fix for zeroprefixed hashes | |||
2013-07-16 | adapt srp account_flow test for the api to new ruby_srp API | Azul | |
2013-07-16 | ensure the page has been reloaded before testing current_path | Azul | |
This test would fail sometimes on assert_equal '/', current_path I believe it was a timing issue. page.has_content? will wait for the content to show up. So afterwards the current_path should always be correct. |