Skip to content
This repository has been archived by the owner on Sep 30, 2023. It is now read-only.

Support access revocation in OrbitDB access controller #6

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

haadcode
Copy link
Member

This PR will add access revocation support for the OrbitDB Access Controller.

This PR, and approach in general, is still very much WIP.

@haadcode
Copy link
Member Author

Depends on https://github.com/orbitdb/orbit-db-access-controller-store (new repo coming along with this PR)

@haadcode
Copy link
Member Author

There's still bunch of things to consider here and more tests need to be added (especially for access revocation under network partition / when DBs diverge).

I think it'd make sense to reduce the complexity down a bit and remove the "capabilities" part (=various "access" levels) and consider access to write either granted or revoked. The different roles/access levels don't make much sense as they're tied to canAppend()'s functionality (eg. canAppend determines which ac level is allowed to append, so it's always a fixed level/set of levels).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant