Session management with configurable timeout policies
ART-1362_KNOWLEDGE_NODE-2
session token; it does not reference any dev user or customer. At the time of the token generation, the corresponding dev user can define the expiration time of the token. The lifetime of an AAT is usually in days. The subject of the AAT is set to the DON of the application, which is service account (for example, `don:identity:dvrv-us-1:devo/0:svcacc/gG88A`).\n\n  * **System User Token (SUT)** : Uniquely identifies a system user belonging to a dev org. A SUT is obtained by a dev user with the
Authentication — DevRev | Docs
ART-1170_KNOWLEDGE_NODE-3
user with the right level of privileges for a given system user. The SUT is issued for the DON of the corresponding system user. At the time of the token generation, the corresponding dev user can define the expiration time of the token. The lifetime of a SUT is usually in days. The subject of the SUT is set to the DON of the corresponding system user (for example, `don:identity:dvrv-us-1:devo/0:sysu/1`).\n* **Session Token**: Obtained by an application to access DevRev APIs on behalf of a
Authentication | DevRev | Docs
ART-1170_KNOWLEDGE_NODE-4
customer (or customer). The application uses its own AAT to authenticate to the STS to obtain a session token for a customer and then uses that session token to access DevRev APIs. The lifetime of a session token is usually minutes. The subject of the session token is set to the DON of the corresponding customer (for example, `don:identity:dvrv-us-1:devo/0:revo/6:revu/131`).\n* **Personal Access Token (PAT)**: Uniquely identifies a dev user. A PAT can be used by external applications to access
Authentication | DevRev | Docs