summaryrefslogtreecommitdiff
path: root/users/app/models
AgeCommit message (Collapse)Author
2013-07-24separate signup and settings service objects for userAzul
2013-07-24setter for keys for dirty tracking, more robust testsAzul
Just altering identity.keys did not mark identities as changed. Also we now have a sane default for keys.
2013-07-24no need for a remote email classAzul
2013-07-24support deprecated API to set users main identity pgp keyAzul
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-24add keys to identityAzul
2013-07-24remove the remainders of email aliases and forward from userAzul
2013-07-24allow available and unique forwards onlyAzul
2013-07-24validations of email format and local domain moved overAzul
2013-07-24local email adds domain if neededAzul
2013-07-24testing all versions of emial identities, emails are now stringsAzul
2013-07-24move identity creation into user classAzul
It's always based on a user and most default values are based on user properties.
2013-07-24first take on identity model - still brokenAzul
2013-07-16prevent _ prefixes for couchDB document idsAzul
2013-07-08Merge branch 'master' into feature/disable_accountjessib
Conflicts: users/app/controllers/users_controller.rb users/app/helpers/users_helper.rb users/app/views/users/edit.html.haml users/app/views/users/show.html.haml users/config/locales/en.yml
2013-07-04allow forms with blank email forward.elijah
2013-07-03Accounts can be enabled or not. Admins can edit this property.jessib
2013-04-25Merge pull request #40 from azul/feature/token-authjessib
Token auth with a database of it's own
2013-04-24renamed and fixed pgp_key viewAzul
2013-04-09let's use safe ids instead of the default couch onesAzul
Couch uses partly random partly sequential ids by default. We could change that in couch config to be all random. But this is probably more safe.
2013-04-09initial token model and unit testAzul
2013-04-03make sure user tests also run when run from users subdirAzul
* The APP_CONFIG needs to be initialized in core so that is required from other engines * paths for load_views need to be relative to the model - not to rails root.
2013-02-28Have specific error messages for usernames with incorrect formats.jessib
Signed-off-by: jessib <jessib@leap.se>
2013-02-26Changes to valid format for usernames.jessib
2013-02-06using ruby-srp 0.1.5 SRP::Client to wrap user in sessionAzul
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-18more flexible email partialAzul
2013-01-18Merge remote-tracking branch 'origin/master' into feature/fixed-email-addressAzul
Conflicts: users/app/views/emails/_email.html.haml
2013-01-17minor fixes to validation workflowAzul
2013-01-17unit tests passingAzul
2013-01-16incomplete initial changes to make email address just login@domain.tldAzul
This involves a number of other changes like making sure the comparison between aliases and emails still works. Will do that by removing the @domain.tld from aliases as well.
2013-01-14Use partials for displaying details shown when viewing a user. Some of these ↵jessib
partials have specific CSS for another use, so we will likely want to tweak this.
2013-01-14Merge branch 'master' into feature/show_user. Added new tests.jessib
Conflicts: users/test/functional/users_controller_test.rb
2013-01-14got users controller test to pass - tickets controller test next.Azul
2013-01-11basic dummy data for usersAzul
2013-01-08Adding show view for users.jessib
2012-12-22moving the js for view definitions into separate filesAzul
This way we get syntax highlighting and so on.
2012-12-20fixed tests, testing corner cases, fixed theseAzul
2012-12-20this is what += is there forAzul
2012-12-20validating email domain and displaying it as the placeholderAzul
This even works client side. :)
2012-12-18make sure we have email_aliases at all before testing for an error on the lastAzul
2012-12-18refactored email_alias creation and validationAzul
using CouchRests user.email_aliases.build so the casted_by method is set in the alias Used this to move the validations into the alias itself. This is where they belong and allows us to render the errors inline along the email field they belong to.
2012-12-17enabled destroying email aliases - no ajax yet.Azul
2012-12-13Merge branch 'feature/email-aliases-model'Azul
2012-12-13use the same partial for Email and LocalEmailAzul
2012-12-13refactor: changed add_email to add_email_aliasAzul
that's what it does. Changed all tests to use it instead of the attributes method
2012-12-13refactor: Email constructor now takes string or hashAzul
This allows us to reuse add_email from email_aliases_attributes=
2012-12-13refactor: allow adding email aliases directlyAzul
2012-12-13ensure users do not have duplicate email aliasesAzul
nor aliases that are the same as the original email for that matter
2012-12-13LocalEmail added - will validate uniqueness amongst emails and aliasesAzul