Revoke User Sessions
okta.revoke_user_sessions
ActionBusiness appsconnection required
Calls the Okta API with the connection's credentials.
End every Okta session the user currently holds, and optionally revoke the OAuth and OpenID Connect tokens issued to them.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- API key
- Providers
- Okta
- Secret shape
- the API token, or {"api_token": "…"}
- Config it needs
- org_url
- Resolved by
- config.connection_id, else node.connection_id
Configuration
2 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
user_id The user to act on — an Okta user id, their login, or the login shortname. | string | Yes | — | — | 00u1a2b3c4D5e6F7g8h9 |
oauth_tokens Also revoke the OAuth access and refresh tokens issued to this user. | boolean | No | false | — | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"oauth_tokens": false,
"user_id": "00u1a2b3c4D5e6F7g8h9"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
revoked True once Okta cleared the user's sessions. | boolean | — |
user_id The user whose sessions were cleared. | string | — |
oauth_tokens Whether OAuth tokens were revoked alongside the sessions. | boolean | — |
{
"oauth_tokens": false,
"revoked": false,
"user_id": ""
}See Revoke User Sessions run in a workflow.
In a technical demo we add the Okta connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.