You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Session tokens are attached to requests in RequestMetaHeader by the clients. This token should contain correct owner ID, public key, and token ID. However there is also lifetime field which is most probably ignored. Lifetime expiration is stored in session token copy on storage node, but it is ignored in request.
E.g. when pool sends request, it ignores lifetime but it works fine.
Expiration in token storage affects how long we should store the key, i.e. session lifetime.
At the same time one could create some tokens with a different lifetime but the same session key. In this case I would expect them to stop working after the expiration epoch.
Session tokens are attached to requests in
RequestMetaHeader
by the clients. This token should contain correctowner ID
,public key
, andtoken ID
. However there is also lifetime field which is most probably ignored. Lifetimeexpiration
is stored in session token copy on storage node, but it is ignored in request.E.g. when
pool
sends request, it ignores lifetime but it works fine.Is it okay? It seems like a bug, but
expiration
still checked in session token storage.The text was updated successfully, but these errors were encountered: