Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to impose restricted access based on participants role. #34

Open
mna2016 opened this issue Jul 10, 2017 · 3 comments
Open

How to impose restricted access based on participants role. #34

mna2016 opened this issue Jul 10, 2017 · 3 comments

Comments

@mna2016
Copy link

mna2016 commented Jul 10, 2017

How to have access control at the chaincode level. i.e. If I have 4 users participating in teh use case like Supplier, Transporter, Regulator, End user - How to control the access of these 4 users in chaincode. For example Regulator can see everything. Transporter cannot see data meant for Supplier and End user.

How to have such an access control?

(Ref: I have seen car lease demo another example of IBM blockchain, doing acces control at chaincode level.)

@kletkeman
Copy link
Contributor

Chaincode level is widely regarded as the appropriate mechanism. The "creator" of the transaction is available through the stub API and the fields in there can be used to provide access control. Techniques include denial of the transaction right up front and / or redaction of the response. There is no library for applications yet, however using the Hyperledger Composer for your chain code and applications gives you access to their Access Control Language, which can be used to do most or all of what you want I believe.

@mna2016
Copy link
Author

mna2016 commented Jul 11, 2017

I am implementing blockchain service hosted on bluemix. So I guess I cannot use the hyperledger composer option(Please correct me if I am not).
I will try to use the available "owner\creator" field to have access restriction checks inside of chaincode.

Thanks!

@kletkeman
Copy link
Contributor

The Hyperledger Composer is compatible with both fabric v0.6 and fabric v1, and v0.6 is being deprecated and removed from Bluemix fairly soon. Composer is compatible with Bluemix fabrics, with deployment and communication going through a connection profile designed for Bluemix. I suggest that you read the rocket chat channel for composer here: https://chat.hyperledger.org/channel/composer and ask Composer questions there. They are pretty responsive.

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

No branches or pull requests

2 participants