You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
Can we make the assumption that Joost already knows that Dimitri is working with B?
If not, the provider needs to know all users of every trusted user which is a problem.
If yes, can we make the assumption that Joost already knows the unique identifier of Dimitri on B?
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.
If yes, can we use the e-mailaddress as the unique identifier per platform?
If not, what can we use as the unique identifier per platform?
The text was updated successfully, but these errors were encountered:
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:The text was updated successfully, but these errors were encountered: