https://github.com/artus/bcdb-authz
Enabling external asset authorization using blockchain technology.
https://github.com/artus/bcdb-authz
authorization bcdb-authz bigchaindb blockchain role-based-access-control transaction
Last synced: about 2 months ago
JSON representation
Enabling external asset authorization using blockchain technology.
- Host: GitHub
- URL: https://github.com/artus/bcdb-authz
- Owner: artus
- Created: 2018-03-15T09:24:51.000Z (about 7 years ago)
- Default Branch: master
- Last Pushed: 2018-05-29T11:55:01.000Z (almost 7 years ago)
- Last Synced: 2025-02-09T10:31:24.449Z (3 months ago)
- Topics: authorization, bcdb-authz, bigchaindb, blockchain, role-based-access-control, transaction
- Language: TypeScript
- Size: 1.2 MB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
![]()
[](https://travis-ci.org/artus/bcdb-authz)
# bcdb-authz
## Using blockchain as an Authorization layer.With `bcdb-authz`, you can use BigchainDB as an authorization layer among different peers. Each file you want to author using `bcdb-authz` gets assigned a unique identifier, which will result in an asset that you can chain transactions on that alter the rights for different users. Users are also identified using a unique identifier, but are not stored as an asset on the BigchainDB network.
This library is still in development, so check back later to see a working version!## How does it work?
BigchainDB uses transactions to alter the state of an asset. In this case, a transaction is used to `grant` or `revoke` permissions to a certain user identifier. Iterating over all transactions of a certain asset will result in the latest map containing permissions for each user that was granted permissions. Each transaction also includes a date in the metafield, which enables functionality to look at certain permissions at a specific point in time.