curl --request POST \
--url https://{cluster}.cognitedata.com/api/v1/projects/{project}/sessions/revoke \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"items": [
{
"id": 123
}
]
}
'{
"items": [
{
"id": 0,
"type": "CLIENT_CREDENTIALS",
"status": "REVOKED",
"creationTime": 1638795554528,
"expirationTime": 1638795554528,
"clientId": "client-123"
}
]
}Required capabilities:
sessionsAcl:DELETE
Revoke access to a session. Revocation is idempotent. Revocation of a session may in some cases take up to 1 hour to take effect.
curl --request POST \
--url https://{cluster}.cognitedata.com/api/v1/projects/{project}/sessions/revoke \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '
{
"items": [
{
"id": 123
}
]
}
'{
"items": [
{
"id": 0,
"type": "CLIENT_CREDENTIALS",
"status": "REVOKED",
"creationTime": 1638795554528,
"expirationTime": 1638795554528,
"clientId": "client-123"
}
]
}Access token issued by the CDF project's configured identity provider. Access token must be an OpenID Connect token, and the project must be configured to accept OpenID Connect tokens. Use a header key of 'Authorization' with a value of 'Bearer $accesstoken'. The token can be obtained through any flow supported by the identity provider.
A request containing the information needed to revoke sessions.
1Show child attributes
List of revoked sessions.
If the user does not have the sessionsAcl:LIST capability, then only the session IDs will be present in the response.
Was this page helpful?