e2e guide: remove refs to refresh tokens

refresh tokens are d34d
This commit is contained in:
Richard van der Hoff 2016-10-18 16:06:22 +01:00 committed by GitHub
parent 21888b5542
commit 703b782ea1

View file

@ -41,12 +41,11 @@ response; a client is also free to generate its own ``device_id`` or, as
above, reuse a device, in which case the client should pass the above, reuse a device, in which case the client should pass the
``device_id`` in the request body. ``device_id`` in the request body.
The lifetime of devices and ``access_token``\ s (technically: chains of The lifetime of devices and ``access_token``\ s are closely related. In
``refresh_token``\ s and ``access_token``\ s), are closely related. In
the simple case where a new device is created each time you log in, the simple case where a new device is created each time you log in,
there is a one-to-one mapping between a ``device_id`` and an there is a one-to-one mapping between a ``device_id`` and an
``access_token`` chain. If a client reuses a ``device_id`` when logging ``access_token``. If a client reuses a ``device_id`` when logging
in, there will be several ``access_token`` chains associated with a in, there will be several ``access_token``\ s associated with a
given ``device_id`` - but still, we would expect only one of these to be given ``device_id`` - but still, we would expect only one of these to be
active at once (though we do not currently enforce that in Synapse). active at once (though we do not currently enforce that in Synapse).