1. 05 Dec, 2021 1 commit
  2. 12 Feb, 2021 2 commits
  3. 19 Jan, 2021 1 commit
  4. 05 Feb, 2020 1 commit
    • ale's avatar
      Add API to disable users · 51e37609
      ale authored
      The user and all associated resources will have their status set to
      'inactive'.
      
      Fixes issue #12.
      51e37609
  5. 16 Nov, 2019 1 commit
    • 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
  6. 26 Aug, 2019 2 commits
  7. 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
  8. 13 Jun, 2019 1 commit
  9. 09 Jun, 2019 3 commits
  10. 03 Feb, 2019 1 commit
    • ale's avatar
      Add a SearchResource API · dd4cfa28
      ale authored
      To support pattern searches, make the LDAP query templates understand
      both "admin-provided input" and "user-provided input", so that
      wildcards will only be escaped in the latter case.
      dd4cfa28
  11. 14 Dec, 2018 2 commits
  12. 14 Nov, 2018 1 commit
  13. 09 Nov, 2018 2 commits
    • ale's avatar
      Rename PasswordRecovery to AccountRecovery · ec82ed43
      ale authored
      Referring to the account is clearer. Also add account recovery
      integration tests, and a test fixture with encryption keys.
      ec82ed43
    • ale's avatar
      First stage of refactor targeting simplicity · 4e34034b
      ale authored
      Structure flow around requests themselves and composition rather than
      handlers and wrappers, the results are likely more readable (and
      shorter).
      
      Move all the user auth management business logic to a smart RawUser
      object, to separate it from details of API handling. The result should
      be more understandable: all critical changes are contained within a
      single type.
      
      Also, with all the workflow driven by Requests, we can get rid of the
      boilerplate in the HTTP API server and replace it with a tiny tiny
      layer of reflection.
      4e34034b
  14. 29 Oct, 2018 1 commit
  15. 28 Oct, 2018 1 commit
  16. 02 Jul, 2018 1 commit
  17. 30 Jun, 2018 1 commit
  18. 26 Jun, 2018 3 commits
  19. 24 Jun, 2018 1 commit
  20. 23 Jun, 2018 2 commits
  21. 22 Jun, 2018 1 commit
    • ale's avatar
      Add integration tests · aef048c2
      ale authored
      Start a full HTTP server, backed by an in-memory LDAP server, and test
      the API directly.
      aef048c2
  22. 20 Jun, 2018 1 commit
  23. 02 Apr, 2018 1 commit
  24. 01 Apr, 2018 2 commits
  25. 20 Mar, 2018 1 commit
  26. 18 Mar, 2018 1 commit