Confirmed users
927
edits
CloudServices/Sagrada/TokenServer: Difference between revisions
Jump to navigation
Jump to search
CloudServices/Sagrada/TokenServer (view source)
Revision as of 23:12, 11 January 2012
, 11 January 2012→Flow
Tarek.ziade (talk | contribs) |
Tarek.ziade (talk | contribs) (→Flow) |
||
| Line 124: | Line 124: | ||
* the client saves the node location and oauth parameters to use in subsequent requests. [6] | * the client saves the node location and oauth parameters to use in subsequent requests. [6] | ||
* for each subsequent request to the Service, the client calculates a special Authorization header using two-legged OAuth [7] and sends the request to the allocated node location [8] along with the metadata token if provided | * for each subsequent request to the Service, the client calculates a special Authorization header using two-legged OAuth [7] and sends the request to the allocated node location [8] along with the metadata token if provided, in an ''X-App-Metadata''. | ||
POST /request HTTP/1.1 | POST /request HTTP/1.1 | ||
Host: some.node.services.mozilla.com | Host: some.node.services.mozilla.com | ||
Authorization: OAuth realm="Example", | Authorization: OAuth realm="Example", | ||
oauth_consumer_key=<auth-token> | oauth_consumer_key=<auth-token> | ||
oauth_signature_method="HMAC-SHA1", | oauth_signature_method="HMAC-SHA1", | ||
| Line 135: | Line 134: | ||
oauth_nonce="7d8f3e4a", | oauth_nonce="7d8f3e4a", | ||
oauth_signature="bYT5CMsGcbgUdFHObYMEfcx6bsw%3D" | oauth_signature="bYT5CMsGcbgUdFHObYMEfcx6bsw%3D" | ||
X-App-Metadata: <metadata-token> | |||
* the node uses the Signing Secret to validate the Auth Token [9]. If invalid or expired then the node returns a 401 | * the node uses the Signing Secret to validate the Auth Token [9]. If invalid or expired then the node returns a 401 | ||