1. 21 May, 2013 1 commit
  2. 15 May, 2013 2 commits
    • Kostas Papadimitriou's avatar
      astakos: User activation flow improvements · 7319c9be
      Kostas Papadimitriou authored
      Major refactoring on user email verification/activation process
      Activation logic moved from dispersed code in functions/view modules to
      ActivationBackend methods. All user activation handling code in astakos views
      and command line utilities was updated to use activation backend instances.
      User moderation takes place right after user has verified the email address used
      during the signup process. This solves issues caused when users signed up using
      an existing but not yet verified email, causing invalidation of previously
      moderated accounts.
      A bunch of new fields added in AstakosUser model. Those fields added to clear up
      a bit the identification of user status at a given time and additionaly keep
      track of when specific user actions took place as a reference for
      administrators. The following section contains detailed description of each
      introduced field.
      Introduced AstakosUser fields
      Fields get properly set across sigup/activation/moderation processes.
      * verification_code
        Unique identifier used instead of user auth token in user email
        verification url. This is initially set when user signup and gets updated
        each time a new verification mail is sent (requested either by admin or user)
      * verified_at
        The date user email got verified.
      * moderated
        Whether or not the used passed through moderation process.
      * moderated_at
        The date user got moderated.
      * moderated_data
        A snapshot of user instance by the time of moderation (in json format).
      * accepted_policy
        A string to identify if user was automatically moderated/accepted.
      * accepted_email
        The email used during user activation.
      * deactivated_reason
        Reason user got deactivated, provided by the administrator.
      * deactivated_at
        Date user got deactivated.
      * activated_at
        Date user got activated.
      * is_rejected
        Whether or not account was rejected.
      South data migration included.
      Handles user entries as follows
      Users with no activation_sent date
      - Generate and fill verification_code field.
      - Once user will visit the activation url an additional moderation step
        will be required to activate the user.
      Users with verified email which are not active
      - Set moderated to True
      - Set is_active to False
      - Set moderated_at to user.auth_token_created
      - Set accepted_email to user.email
      - Set accepted_policy to 'migration'
      - Set deactivated_reason to "migration"
      - Set deactivated_at to user.updated
      Users with verified email which are active
      - Set moderated to True
      - Set moderated_at to user.auth_token_created
      - Set accepted_policy to 'migration'
      - Set accepted_email to user.email
      - Set verified_at to user.moderated_at
      Users with no verified email and activation_sent set
      - Set moderated to True
      - Set moderated_at to user.updated
      - Set verification_code to user.auth_token (to avoid invalidating old
        activation urls)
      Updated management commands
      - New options --pending-moderation, --pending-verification added in `user-list`
      - New fields verified/moderated included in `user-list` command.
      - New moderation options `--accept`/`--reject` added in `user-modify` command.
        `--reject` can optionally be combined with `--reject-reason`.
      Other changes
      - Cleaned up explicit smtp error handling when sending email notifications.
      - Prevent already signed in users from using an account activation url
      - Allow user to logout even when latest terms where not accepted
      - Renamed templates
          * helpdesk_notification.txt -> account_activated_notification.txt
          * account_creation_notification.txt ->
      - Updated im tests
    • Kostas Papadimitriou's avatar
  3. 30 Apr, 2013 1 commit
  4. 26 Apr, 2013 1 commit
  5. 19 Apr, 2013 1 commit
  6. 26 Mar, 2013 1 commit
  7. 27 Feb, 2013 1 commit
  8. 28 Jan, 2013 1 commit
    • Giorgos Korfiatis's avatar
      Make Chain a proper db table · 0cff9d3f
      Giorgos Korfiatis authored
      Keep chain IDs in table Chain and add foreign keys from ProjectApplication
      and Project to Chain.
      This will allow us to reference a possibly not yet approved project
      in a more concise way.
  9. 24 Jan, 2013 1 commit
  10. 16 Jan, 2013 1 commit
  11. 15 Jan, 2013 1 commit
  12. 14 Jan, 2013 1 commit
    • Giorgos Korfiatis's avatar
      Changes in registering to quotaholder · 9ceda73b
      Giorgos Korfiatis authored
      Add an 'uplimit' (default) field in Resource;
      change AstakosUserQuota fields to IntDecimalField;
      pass all four limits of initial quotas to the quotaholder;
      register services and resources explicitly upon creation;
      a wrapper for get_quota.
  13. 11 Jan, 2013 8 commits
  14. 10 Jan, 2013 1 commit
  15. 08 Jan, 2013 1 commit
  16. 28 Dec, 2012 1 commit
  17. 27 Dec, 2012 1 commit
  18. 19 Dec, 2012 1 commit
  19. 18 Dec, 2012 1 commit
  20. 17 Dec, 2012 1 commit
  21. 11 Dec, 2012 1 commit
    • Kostas Papadimitriou's avatar
      Third party login providers fixes/improvements · f5acbf60
      Kostas Papadimitriou authored
      - Store additional provider info in PendingThirdPartyUser entries
      - Include third party registration logic in main signup view. Additional
        per provider signup views removed.
      - Unique email validation for all activation backend forms
      - Keep created dates in auth provider and pending user entries
      - Other minor fixes
  22. 04 Dec, 2012 2 commits
  23. 30 Nov, 2012 2 commits
  24. 10 Sep, 2012 1 commit
  25. 29 Aug, 2012 1 commit
  26. 19 Jul, 2012 1 commit
  27. 01 Jun, 2012 1 commit
  28. 30 May, 2012 1 commit
    • Sofia Papagiannaki's avatar
      Register the date a user activation email sent and reset it when the user... · 4a3321c6
      Sofia Papagiannaki authored
      Register the date a user activation email sent and reset it when the user becomes active (for future use)
      This field can have the following values:
      * epoch:						signifies the user has been created before adding the specific field (so we have no actually information whether an activation email has been sent or not)  
      * NULL:							signifies the user is active or no activation email has been sent
      * other date (except epoch):	 the date the activation email sent
      Passing the -n option in list users snf command shows only the new users (created after adding the field) who have not received an activation.
      Refs: #2471
  29. 22 May, 2012 1 commit
  30. 07 May, 2012 1 commit