Fig-26: Alice Prepares ePortfolio.
The invitation based approach is modelled after the Liberty Alliance [], [].
Fig-26: Alice Prepares ePortfolio.
Assume Alice has used ePortfolio Front End to construct some artifacts about her career (see Fig-26), including attestation from University A that she has a degree, and some exhibits, in Album A of the work she has already done.
Fig-27: Bob using Alice's Web Services by way of invitation.
Now, Alice can invite her job coach Bob to access these artifacts as Web Services, see Fig-27. First Bob resolves the invitation to the necessary access tokens and then accesses the services. Bob is acting through the Job Search Front End.
On access (2a) two tokens will be present
Delegation Token, encrypted for Album A and usable by Job Search, containing Alice's pseudonym at Album A. This token indicates that the access is by invitation and not by Alice being present in the transaction. The Delegation token can also include description of which part of the user's resource at the Service Provider can be accessed and how.
Token, encrypted for Album A and usable by Job Search, containing Bob's pseudonym at Album A. This token indicates that Bob is performing the operation and that Bob is present in the transaction (at front channel).