1. 05 Dec, 2021 1 commit
  2. 25 Aug, 2021 1 commit
  3. 12 Feb, 2021 1 commit
  4. 26 Apr, 2020 1 commit
  5. 09 Apr, 2020 1 commit
  6. 08 Apr, 2020 2 commits
  7. 15 Jan, 2020 2 commits
  8. 16 Nov, 2019 2 commits
    • ale's avatar
      Split availability check from user validation too · eef4b6e1
      ale authored
      And fix an issue where validHostedEmail() was no longer checking for
      availability in email alias validation.
      eef4b6e1
    • ale's avatar
      Add an UpdateResource action · 0bb4fb1e
      ale authored
      Since this requires validating an *existing* resource, we also split
      out the availability checks in the validation code from the
      syntactical validation, which is a good thing anyway.
      0bb4fb1e
  9. 08 Nov, 2019 1 commit
  10. 26 Oct, 2019 1 commit
  11. 20 Oct, 2019 1 commit
  12. 18 Oct, 2019 1 commit
  13. 16 Oct, 2019 1 commit
  14. 14 Oct, 2019 1 commit
  15. 22 Aug, 2019 1 commit
    • ale's avatar
      Add missing validations and an availability API endpoint · b790a71a
      ale authored
      Previously some resource types were not validating requests for
      uniqueness (the creation would have failed later, at database commit
      time).
      
      The availability API allows unauthenticated callers (i.e. everyone) to
      query for existence of a specific resource, or resources that would
      conflict with it in the global namespace. It's basically a public
      validation check, meant so that applications that let users create
      accounts can provide early feedback on availability.
      b790a71a
  16. 03 Aug, 2019 1 commit
  17. 05 May, 2019 1 commit
  18. 18 Nov, 2018 3 commits
  19. 17 Nov, 2018 1 commit
    • ale's avatar
      Switch to really opaque ResourceIDs · 78d08eef
      ale authored
      The new ResourceID is really a database ID (in our case, a LDAP DN),
      and we have completely decoupled other request attributes like type
      and owner from it.
      
      Resource ownership checks are now delegated to the backend.
      
      Also change the backend CreateResource call to CreateResources, taking
      multiple resources at once, so we can perform user-level resource
      validation, and simplify the CreateUser code path.
      78d08eef
  20. 14 Nov, 2018 1 commit
  21. 09 Nov, 2018 1 commit
  22. 31 Oct, 2018 1 commit
  23. 26 Jul, 2018 1 commit
  24. 01 Jul, 2018 1 commit
    • ale's avatar
      Add unix user IDs to object types · e15acb1e
      ale authored
      Adds UIDs to users, websites, DAV accounts.
      
      Assign a random UID to newly created users, and ensure that all
      associated resources have the same UID as well.
      e15acb1e
  25. 28 Jun, 2018 1 commit
  26. 25 Jun, 2018 1 commit
  27. 24 Jun, 2018 4 commits
  28. 21 Jun, 2018 2 commits
  29. 20 Jun, 2018 1 commit
    • ale's avatar
      Plug validators back in · a0c1b63b
      ale authored
      The new Backend/TX split makes it a bit harder to test the validators,
      but do so anyway.
      a0c1b63b
  30. 10 Jun, 2018 1 commit
    • ale's avatar
      Add validators for request fields · 5ffe2e08
      ale authored
      This includes a number of validators meant to support the creation of
      new users and resources (for instance by checking for resource ID
      uniqueness etc).
      5ffe2e08