1. 15 Oct, 2013 1 commit
  2. 04 Oct, 2013 1 commit
  3. 27 Sep, 2013 1 commit
    • Ilias Tsitsimpis's avatar
      Fix a python syntax error · 1bea338c
      Ilias Tsitsimpis authored
      In python 2 we cannot have keyword-only arguments (PEP 3102).
      And even if we could, this was not the right way to
      declare a python function.
      1bea338c
  4. 26 Sep, 2013 1 commit
    • Ilias Tsitsimpis's avatar
      astakos: Fix `save() got unexpected argument' · 232b2aa9
      Ilias Tsitsimpis authored
      From Django documentation:
      """
      It’s also important that you pass through the arguments that can be
      passed to the model method – that’s what the *args, **kwargs bit does.
      Django will, from time to time, extend the capabilities of built-in
      model methods, adding new arguments. If you use *args, **kwargs in your
      method definitions, you are guaranteed that your code will automatically
      support those arguments when they are added.
      """
      232b2aa9
  5. 18 Jul, 2013 1 commit
  6. 28 Jun, 2013 1 commit
  7. 07 Jun, 2013 1 commit
  8. 04 Jun, 2013 3 commits
  9. 03 Jun, 2013 3 commits
  10. 27 May, 2013 1 commit
  11. 23 May, 2013 2 commits
  12. 21 May, 2013 3 commits
  13. 20 May, 2013 5 commits
  14. 15 May, 2013 3 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`
        command.
      - 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 ->
              account_pending_moderation_notification.txt
      - Updated im tests
      7319c9be
    • Kostas Papadimitriou's avatar
      44a40b77
    • Giorgos Korfiatis's avatar
      astakos: Remove membership policy settings · b0eb658d
      Giorgos Korfiatis authored
      Available join and leave policies are internally defined and should
      not be changed by settings. Move policy descriptions to presentation.py.
      
      Do not convert to string the lookup key in templatetags/filters.py
      b0eb658d
  15. 14 May, 2013 1 commit
    • Giorgos Korfiatis's avatar
      astakos: Remove command user-set-initial-quota · fc5e138f
      Giorgos Korfiatis authored
      To change base quota for a specified user:
        snf-manage user-modify user --set-base-quota resource limit
      
      To import base quota in batch from a file:
        snf-manage astakos-quota --import-base-quota filename
      
      Rename `initial' to `base quota' in command output.
      Move code that creates/removes AstakosUserQuota entries in file quotas.py;
      sync user to quotaholder after such a change.
      
      Refs #3411
      fc5e138f
  16. 13 May, 2013 1 commit
  17. 10 May, 2013 1 commit
  18. 08 May, 2013 2 commits
  19. 02 May, 2013 2 commits
  20. 01 May, 2013 1 commit
  21. 30 Apr, 2013 2 commits
    • Kostas Papadimitriou's avatar
      astakos: Resources metadata improvements · 93fe15e0
      Kostas Papadimitriou authored
      - Allow admin to overwrite default resources presentation data using
        ASTAKOS_RESROUCES_META setting. dict_merge is used to accomodate admin
        from declaring all available metadata parameters.
      - Enforce allow_in_projects resource policy in project application
        form.
      93fe15e0
    • Giorgos Korfiatis's avatar
      astakos: Control exposing resources in projects · bf797336
      Giorgos Korfiatis authored
      Add attribute `allow_in_projects' in Resource model (True by default).
      Set this flag for astakos.pending_app to False in the description
      of astakos resources.
      bf797336
  22. 25 Apr, 2013 1 commit
  23. 23 Apr, 2013 1 commit
  24. 22 Apr, 2013 1 commit