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 does a provider know where to send the invitation to? #26

Closed
dvh opened this issue Dec 14, 2016 · 1 comment
Closed

How does a provider know where to send the invitation to? #26

dvh opened this issue Dec 14, 2016 · 1 comment

Comments

@dvh
Copy link

dvh commented Dec 14, 2016

In all our proposals we assume that the invitation object contains a user identifier which exists at the given endpoint. If we don't want to expose users via the API because we want to keep the attack surface as small as possible (described in issue #23), then how does a user know where to send the invitation to? In other words, if Joost (user on A) wants to share a resource with Dimitri (user on B), then:

  1. Can we make the assumption that Joost already knows that Dimitri is working with B?
    1. If not, the provider needs to know all users of every trusted user which is a problem.
    2. If yes, can we make the assumption that Joost already knows the unique identifier of Dimitri on B?
      1. If not, we could perform a user search on B (because we know that Dimitri is working with B) and we don't want to do that due to the size of the attack surface.
      2. If yes, can we use the e-mailaddress as the unique identifier per platform?
        1. If not, what can we use as the unique identifier per platform?
@dvh
Copy link
Author

dvh commented Jan 26, 2017

As discussed we assume the receiving user/group and receiving platform are known by the sender before creating the share.

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

1 participant