1. 09 Nov, 2018 1 commit
    • 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
      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.
  2. 01 Nov, 2018 1 commit
  3. 17 Aug, 2018 1 commit
  4. 01 Jul, 2018 3 commits
  5. 30 Jun, 2018 2 commits
  6. 26 Jun, 2018 1 commit
    • ale's avatar
      Minor refactoring of LDAP query templates · 11cab73f
      ale authored
      Rename queryConfig to queryTemplate to better reflect its purpose, and
      drop all cruft that had to do with config deserialization.
  7. 24 Jun, 2018 1 commit
  8. 23 Jun, 2018 1 commit
    • ale's avatar
      Add password recovery logic · 3a30acc6
      ale authored
      Implement a password recovery endpoint, and a way to set the recovery
      hints (in the current model, it's a hint/response system).
  9. 22 Jun, 2018 3 commits
  10. 21 Jun, 2018 2 commits
  11. 20 Jun, 2018 1 commit
    • ale's avatar
      Refactor the LDAP backend · 02d7c9c6
      ale authored
      Use a lower level type to abstract LDAP "transactions" (really just
      batches of changes) and generate a set of ModifyRequest objects at
      commit time. Change the API to let the caller manage the
      transaction (TX object) lifetime.
  12. 19 Jun, 2018 1 commit
    • ale's avatar
      Implement a transaction-like interface for the backend · ac2aa256
      ale authored
      This should make it easier to implement a SQL backend in the future if
      necessary, even though LDAP knows no such thing as transactions.
      As a result of a better low-level interface, reducing the boilerplate
      LDAP code, the business logic in model.go should be quite more
  13. 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).
  14. 02 Apr, 2018 2 commits
  15. 01 Apr, 2018 1 commit
  16. 20 Mar, 2018 1 commit
  17. 18 Mar, 2018 1 commit