silkroadnomad/deContact

AccessController: db owner and record owner should be allowed to (over)write

Opened this issue · 0 comments

The idea is:

  1. Alice can write when ever she wants to write
  2. When she requests the address of Bob, she allows him to write by adding a dummy record an attribute owner: did of bob

if bob then opens Alice db, the accesscontroller could (if possible) open Alice db and check if there is a record with his did and then return true (for adding or deleting)
meaning the writing identity should be equal with one record in Alice db

Question so far: On Bob's side when address book is opened, it must be replicated right in the moment the access controller is checking the data. This might be a bit of a thing