1. 09 Feb, 2020 3 commits
  2. 25 May, 2019 1 commit
  3. 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
  4. 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
  5. 01 Nov, 2018 1 commit
    • ale's avatar
      Use a custom u2f.Registration wrapper type that serializes to JSON · 50f6eaa4
      ale authored
      Establish a standardized serialization format for u2f registration
      keys: base64-encoded raw registration data, encoded as a JSON
      string. This format decodes transparently to a Go []byte slice, but it
      needs explicit base64 decoding in Python.
      50f6eaa4
  6. 31 Oct, 2018 1 commit
  7. 17 Aug, 2018 1 commit
  8. 02 Jul, 2018 1 commit
  9. 01 Jul, 2018 3 commits
  10. 30 Jun, 2018 3 commits
  11. 26 Jun, 2018 3 commits
  12. 25 Jun, 2018 1 commit
  13. 24 Jun, 2018 4 commits
  14. 23 Jun, 2018 5 commits
  15. 22 Jun, 2018 1 commit
  16. 21 Jun, 2018 2 commits
  17. 20 Jun, 2018 3 commits
    • ale's avatar
      Fix the server package for the new backend API · 2ce591e6
      ale authored
      2ce591e6
    • 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
    • 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.
      02d7c9c6
  18. 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
      readable.
      ac2aa256
  19. 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
  20. 02 Apr, 2018 2 commits