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

Create share by e-mail after invitation accepted #1484

Closed
mirekys opened this issue Feb 17, 2021 · 2 comments
Closed

Create share by e-mail after invitation accepted #1484

mirekys opened this issue Feb 17, 2021 · 2 comments
Assignees
Labels
feature New feature

Comments

@mirekys
Copy link
Member

mirekys commented Feb 17, 2021

Scenario

  1. Let's assume we have user A who starts the invitation workflow by sending an invite link to user B's e-mail b@example.org he knows.
  2. User B accepts the invite link by going through mesh directory and logging into his provider of choice
  3. User A now wants to share something to B
  4. At this moment, user A still knows only the user B's e-mail (b@example.org)

The problem

User A has currently no means of determining grantee.opaqueid used in the invitation sharing workflow, he doesn't even know which provider.idp was used by user B to accept the invite.

  1. User A should be able to create a share for the user B by using the e-mail adress used in the invitation workflow:
$ cmd/reva/reva -insecure ocm-share-create -grantee b@example.org /home/test

or/and

  1. User A should be able to list remote users that accepted the invites he sent. Such accepted invite records should contain some label, that helps user A to recognize, who actually accepted the invite using which invite link (the label would be the used e-mail address b@example.com in this case). User A could then find all necessary sharing details about user B (provider & opaqueid) in this listing based on the label he already knows and any additional user info exchanged at the moment the invite was accepted.
@mirekys mirekys added the feature New feature label Feb 17, 2021
@labkode
Copy link
Member

labkode commented Feb 17, 2021

@mirekys can you start implementing option 2)? This is the foundation

@mirekys
Copy link
Member Author

mirekys commented Mar 16, 2021

Implemented in #1527

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

No branches or pull requests

3 participants