Changes between Version 7 and Version 8 of MashMyData/OAuth


Ignore:
Timestamp:
12/07/10 14:15:33 (9 years ago)
Author:
pjkersha
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MashMyData/OAuth

    v7 v8  
    2323 1. The Portal re-issues its request to the WPS but this time with the Access Token.  The WPS accepts this request: the Portal is acting on behalf of the user. 
    2424 1. The WPS requires data from the CEDA TDS in order to execute its processing job.  It makes a request but gets an unauthorized response. 
    25  1. Following the same procedure, the WPS in the same way as the portal did earlier, gets delegated authority to act on behalf of the user.  Note that this time an alternate path is shown at the Portal Trust Registry.  The registry has no entry for the WPS for this user.  It makes a request to the user to get approval.  This is over some other protocol to HTTP: e-mail, SM or other.  This protocol has security implications so its nature is TBD. 
     25 1. Following the same procedure, the WPS in the same way as the portal did earlier, gets delegated authority to act on behalf of the user.  Note that this time an alternate path is shown at the Portal Trust Registry.  The registry has no entry for the WPS for this user.  It makes a request to the user to get approval.  This is over some other protocol to HTTP: e-mail, SMS or other.  This protocol has security implications so its nature is TBD. 
    2626 1. The end result of the delegation process for the WPS is that it gets an OAuth Access Token which it can use to submit to the TDS. 
    2727 1. The TDS accepts this and allows the WPS to act on behalf of the user.