Type of the device.
Type of the location.
Deletes user session.
Subject.
Id of the session.
Storage should treat sessionId
as untrusted and
perform SQLi and XSS validations before deleting meta data.
Deletes all sessions of the subject
.
Subject.
Number of deleted sessions.
Insert user session in the storage.
IMPORTANT!
It's highly advisable to hashsessionId
before storing it in the database, especially if RDBMS is used.
Subject.
Session id.
Session meta data.
Session ttl (in seconds).
Read session meta data from storage.
Subject.
Id of the session.
Storage should treat sessionId
as untrusted and
perform SQLi and XSS validations before query meta data.
User session meta data or null / undefined if not found.
Read all of the active user sessions for subject
.
Subject user sessions are belonging to.
Session id with the session metadata.
When subject
has no active sessions, returns an empty map.
Caller will pass an UserSessionMetaData object (the same one which was obtained from UserSessionsStorage.read operation, without being cloned)
which has updated UserSessionMetaData.accessedAt field.
Storage needs to replace existing metadata with the passed one.
Notice that this is a safe operation, because other fields are readonly.
Subject.
Id of the session.
Storage should treat sessionId
as untrusted and
perform SQLi and XSS validations before updating meta data.
Session metadata with updated value of the UserSessionMetaData.accessedAt field.
Storage where user sessions are stored.