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

Access policy for a bindle? #268

Open
npmccallum opened this issue Dec 16, 2021 · 2 comments
Open

Access policy for a bindle? #268

npmccallum opened this issue Dec 16, 2021 · 2 comments

Comments

@npmccallum
Copy link

Has any thought been given to access policy for a bindle?

/_i/{bindle-name}@{parcel-id}

I'm really glad that all parcel fetches are done in the context of a bindle name. This means that the invoice can define access control for both itself and its parcels. A user, for example, should be able to always fetch their own bindles. But they should also allow fetching of bindles selectively for other users (or even other criteria). The access policy for a bindle should include the invoice itself. For example, if a user doesn't have access to a bindle it cannot see either the invoice or any of the parcels.

@thomastaylor312
Copy link
Contributor

This is definitely something we've thought through (see the Authorizable and Authorizer traits), but we haven't implemented this yet. I do have an initial design written up in a HackMD somewhere. Let me grab the relevant info and open up a new issue with it

@thomastaylor312
Copy link
Contributor

Just created #275 with that information

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