1. 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
  2. 12 Nov, 2018 1 commit
  3. 01 Nov, 2018 1 commit
  4. 26 Jul, 2018 1 commit
    • ale's avatar
      Add an explicit Type field to Resources · da871e97
      ale authored
      The type is already encoded in the resource ID, but this is handy for
      API clients so that they do not need to parse resource IDs.
      da871e97
  5. 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.
      02d7c9c6