Changes

Jump to: navigation, search

CloudServices/Sagrada/TokenServer

43 bytes added, 00:34, 12 January 2012
Flow
* the Login Server asks the Users DB if the user is already allocated to a node. [3]
* if the user is not allocated to a node, the Login Server asks a new one to the Node Assignment Server [4]
* the Login Server creates a response with an auth token and corresponding token secret [5] and sends it back to the user. The auth token contains the user id and a timestamp, and is signed using the signing secret. The token secret is derived from the master secret and auth token using HKDF. It also adds the node url in the responseunder ''service_entry'', and optionaly a metadata tokenunder ''metadata''. [6]
HTTP/1.1 200 OK
Confirm
927
edits

Navigation menu