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
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.
User B accepts the invite link by going through mesh directory and logging into his provider of choice
User A now wants to share something to B
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.
User A should be able to create a share for the user B by using the e-mail adress used in the invitation workflow:
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.
The text was updated successfully, but these errors were encountered:
Scenario
The problem
User A has currently no means of determining
grantee.opaqueid
used in the invitation sharing workflow, he doesn't even know whichprovider.idp
was used by user B to accept the invite.or/and
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.The text was updated successfully, but these errors were encountered: