---
title: "Workday OAuth Refresh Token Expiration & Revocation"
description: "Understand Workday OAuth access TTLs, fixed-window refresh token timeouts, token rotation, Enforce 60 Minute Access Token Expiry pitfalls, and revocation tasks."
url: https://kiweely.com/guides/workday-oauth-refresh-token-expiration-rotation-revocation
---

# Managing Workday OAuth Refresh Token Expiration, Rotation, and Revocation

Workday rotates user-delegated OAuth refresh tokens on every exchange while enforcing a fixed absolute Refresh Token Timeout measured from initial sign-in. Learn how access TTLs, Enforce 60 Minute Access Token Expiry, and admin revocation tasks work.

-   **Checked** against Workday on November 15
-   Applies to **Workday Authentication & OAuth**
-   5 min read
-   Published November 15
-   By Kiweely

Workday user-delegated OAuth 2.0 clients issue short-lived Bearer access credentials tied to tenant session timeouts and rotate refresh credentials on every `grant_type=refresh_token` call—while enforcing a **non-sliding absolute ceiling** set by **Refresh Token Timeout (in days)** from the moment the worker first signed in. By contrast, integration clients registered via **Register API Client for Integrations** support **Non-Expiring Refresh Tokens** managed manually by administrators.

Misunderstanding fixed-window refresh lifetimes, concurrent rotation races, or the **Enforce 60 Minute Access Token Expiry** check box causes surprise mid-day logouts across external portals, BI tools, and desktop integrations.

## Lifecycle Comparison: User-Delegated vs. Integration Tokens

Token expiration and rotation behave differently depending on which registration task created the client ([see full task comparison](https://kiweely.com/guides/workday-register-api-client-vs-api-client-for-integrations)):

| Lifecycle Property | User-Delegated (`Register API Client`) | Integration (`Register API Client for Integrations`) |
| --- | --- | --- |
|  **Access Credential Lifetime** | Bound to the worker’s Workday session timeout (or 60 minutes on Extend API Gateway / custom expiry setting) | Short-lived Bearer access credential (typically tied to tenant/gateway TTL), renewed via refresh grant |
|  **Refresh Issuance** | Returned automatically from `/token` after `authorization_code` redemption | Generated manually in UI via **API Client > Manage Refresh Tokens for Integrations** |
|  **Refresh Rotation on Use** |  **Yes:** Every `grant_type=refresh_token` response returns both a new access credential and a new refresh value |  **No** (when **Non-Expiring Refresh Tokens** is selected, the same refresh value is reused across exchanges) |
|  **Absolute Refresh Horizon** |  **Fixed window:** `Refresh Token Timeout (in days)` counts from initial browser sign-in and does **not** extend on refresh | Indefinite when **Non-Expiring Refresh Tokens** is checked, until revoked or regenerated |
|  **Effect of Account Deactivation** | Immediately invalidates refresh and blocks new access issuance | Fails with `invalid_grant` if the bound ISU account is disabled or its username changes |

## Why `Enforce 60 Minute Access Token Expiry` Breaks Interactive Sessions

When configuring **Register API Client**, administrators often see **Enforce 60 Minute Access Token Expiry** (or **Enforce Customized Access Token Expiry** on specialized setups such as Time Kiosks) and assume checking it is a harmless security hardening step.

In Workday’s OAuth implementation, Workday explicitly warns in its Studio and external client setup documentation **not** to select **Enforce 60 Minute Access Token Expiry** for standard ongoing interactive sessions because doing so disables OAuth 2.0 authentication continuity after that 60-minute window rather than merely triggering silent background refreshes. Standard Workday OAuth 2.0 access credentials already obey the normal Workday session timeouts configured tenant-wide (on **Edit Tenant Setup - System** / **Security**) or per account.

Reserve customized minute-level access expiry strictly for ephemeral provisioning flows—such as a manager registering a physical **Workday Time Kiosk** device where the setup credential should self-destruct minutes after pairing.

## Executing a Token Refresh Safely (Rotation & Concurrency)

When a user-delegated Bearer credential expires (returning `401 Unauthorized` on a REST, WQL, or RaaS request), exchange the current refresh credential at your tenant’s **Token Endpoint**:

Works

```
POST /ccx/oauth2/gms/token HTTP/1.1
Host: services1.wd3.workday-host.example
Authorization: Basic T0RRNFpEZGtOekl0TXpoaU1DMDBZbUZt...
Content-Type: application/x-www-form-urlencoded

grant_type=refresh_token&client_id=ODQ4ZDdkNzItMzhiMC00YmFmLTgyNzAtNzljNjM0MDlmNmY2
```

*(Include the URL-encoded `refresh_token` form field carrying the latest refresh value received from Workday.)*

Workday responds with a **new** Bearer credential and a **new** refresh credential:

Works

```
{
  "access_token": "28tyw9mpe7huyyah7gftg4djg",
  "refresh_token": "1fndsc9ezoe4s4rbwrzzobgzw7l3os123o0qn1wckmf7zfv5o9v9r5l",
  "token_type": "Bearer"
}
```

### Preventing Race Conditions on Parallel API Calls

Suppose an external dashboard fires four parallel Workday REST requests (`workers/me`, `timeOffBalances`, `paySlips`, `supervisoryOrganizations`) right after the access credential expires:

1.  All four requests receive `401 Unauthorized`.
2.  Without synchronization, four worker threads simultaneously send `grant_type=refresh_token` with the same refresh string `R1`.
3.  Request 1 wins, receives new pair `(A2, R2)`, and invalidates `R1`.
4.  Requests 2, 3, and 4 arrive milliseconds later with `R1` and fail with `400 Bad Request` (`{"error": "invalid_grant"}`), causing naive error handlers to wipe the user’s session!

**Engineering fix:** Wrap `grant_type=refresh_token` calls in a per-user single-flight lock (in-process promise deduplication for single-node apps, or a short Redis/mutex lock for multi-node backends) and atomically persist `(A2, R2)` before releasing waiting requests. Remember too that once the client’s **Refresh Token Timeout (in days)** elapses from the original sign-in timestamp, `grant_type=refresh_token` will legitimately return `invalid_grant`—at which point your app must redirect the user back to the [Authorize Endpoint](https://kiweely.com/guides/workday-authorization-code-grant-user-delegated-oauth-setup).

## Administrative Inspection and Revocation Tasks

Security administrators control active OAuth credentials from the **View API Clients** report (secured to the **Security Administration** domain in the **System** functional area):

| Scenario | Exact Workday Navigation & Task | Immediate Effect |
| --- | --- | --- |
|  **Revoke one user’s or client’s refresh grants** | `View API Clients` -> **API Clients** tab -> Related Actions on client -> **API Client > Manage Refresh Tokens** | Revokes selected refresh grants so no further access credentials can be minted |
|  **Rotate or revoke an integration ISU refresh grant** | `View API Clients` -> **API Clients for Integrations** tab -> Related Actions -> **API Client > Manage Refresh Tokens for Integrations** | Regenerates or deletes the refresh credential bound to that Integration System User |
|  **Emergency shutoff of an external app** | `View API Clients` -> Related Actions -> **API Client > Edit API Client** (disable client or run **Generate New API Client Secret**) | Blocks all `/authorize` and `/token` exchanges for that client across the tenant |
|  **Offboard a terminated worker** | Disable Workday Account (`Edit Workday Account` or automated termination step; see [termination lifecycle guide](https://kiweely.com/guides/workday-revoke-oauth-tokens-terminated-transferred-workers)) | Invalidates all refresh grants tied to that user and blocks API execution |

## Production Hygiene Checklist

-   **Set realistic `Refresh Token Timeout (in days)`:** Choose `14` to `30` days for workforce tools so active employees aren’t forced through browser SSO every morning, while idle grants still age out predictably.
-   **Never store plaintext Workday refresh grants in browser `localStorage`:** Keep credentials in `HttpOnly`, `Secure` encrypted server cookies or sealed client envelopes.
-   **Distinguish rotation races from true expiry:** Log whether an `invalid_grant` error occurred within milliseconds of a sibling refresh exchange vs. after the configured timeout window (see [Fixing Workday OAuth Errors](https://kiweely.com/guides/workday-oauth-invalid-client-unauthorized-client-redirect-uri)).

In [Kiweely Bridge](https://kiweely.com/bridge/security) (coming next), employee Workday OAuth grants are never stored in a central database table at rest: each user-delegated grant is sealed with AES-256-GCM and decrypted strictly in memory during an active call, giving employees and Workday admins instant revocation control without lingering third-party credential stores.

## Frequently asked questions

### Does exchanging a Workday refresh token extend the overall Refresh Token Timeout?

No. On user-delegated API clients, the Refresh Token Timeout (in days) starts at the initial browser authorization and never slides forward. Even if your app refreshes hourly, the user must re-authenticate at the Authorize Endpoint once that fixed window elapses.

### Why did our OAuth sessions break exactly 60 minutes after sign-in?

An administrator likely checked Enforce 60 Minute Access Token Expiry (or Enforce Customized Access Token Expiry) on Register API Client, or your tenant's user session timeout expired without the client executing a refresh\_token grant.

### What happens if two concurrent worker threads try to use the same refresh token?

Because Workday rotates user-delegated refresh values upon exchange, the second concurrent POST with the superseded refresh value fails with invalid\_grant. Serialize refresh calls per user session with a distributed lock or single-flight mutex.

### How do I immediately revoke all active OAuth tokens for a compromised API client?

Open View API Clients, use the related actions menu on the API client to access Manage Refresh Tokens (or regenerate/disable the API client via Edit API Client), which immediately invalidates downstream refreshes.

## Sources checked

-   [Workday Admin Guide — Register API Clients](https://doc.workday.com/admin-guide/en-us/authentication-and-security/authentication/oauth/dan1370797831010.html)
-   [Workday Admin Guide — Register API Clients for Integrations](https://doc.workday.com/admin-guide/en-us/authentication-and-security/authentication/oauth/dan1370797831458.html)
-   [Workday Admin Guide — Enable Multifactor Authentication in Workday Studio](https://doc.workday.com/admin-guide/en-us/workday-studio/integration-deployment/multifactor-authentication-in-workday-studio/kuh1623937418623.html)

## Related guides

[All guides](https://kiweely.com/guides)

-   [### Register API Client vs. Register API Client for Integrations in Workday Use Register API Client with Authorization Code Grant and PKCE when external apps act on behalf of a signed-in worker. Reserve Register API Client for Integrations for headless background jobs bound to a single Integration System User.](https://kiweely.com/guides/workday-register-api-client-vs-api-client-for-integrations)
-   [### How Workday Terminations and Job Transfers Affect Active OAuth Grants Completing Terminate Employee changes staffing status and security groups on the effective date, while disabling the Workday Account immediately kills active OAuth 2.0 refresh grants. Job transfers dynamically recalculate constrained supervisory permissions without requiring re-login.](https://kiweely.com/guides/workday-revoke-oauth-tokens-terminated-transferred-workers)
-   [### Fixing Workday OAuth invalid\_client, unauthorized\_client, and Redirect URI Errors Resolve Workday OAuth 2.0 handshake errors by matching each exact HTTP error code—invalid\_client, unauthorized\_client, invalid\_grant, and redirect\_uri mismatch—against your View API Clients settings, tenant endpoint URLs, and PKCE S256 verifier.](https://kiweely.com/guides/workday-oauth-invalid-client-unauthorized-client-redirect-uri)
-   [### How to Configure User-Delegated OAuth 2.0 Authorization Code Grant in Workday Register a user-delegated Workday OAuth 2.0 client using Register API Client with Authorization Code Grant, PKCE (S256), and Bearer credentials so external applications authenticate employees through SSO and run under their own Workday permissions.](https://kiweely.com/guides/workday-authorization-code-grant-user-delegated-oauth-setup)

### More guides on More Workday guides

[All 46 guides](https://kiweely.com/guides#more)

-   [Handling Hourly vs. Salaried Workday Absence Plans: Hours, Days, and Partial-Day Requests](https://kiweely.com/guides/workday-hourly-vs-salaried-absence-balances-hours-vs-days)
-   [Why Workday Absence Balances or Time Calculations Don’t Update After a Retro Job Change](https://kiweely.com/guides/workday-time-tracking-absence-retro-recalculation-errors)
-   [Troubleshooting Workday Compensation Cycle Eligibility, Proration, and Bonus Rounding Mismatches](https://kiweely.com/guides/workday-advanced-compensation-eligibility-bonus-rounding-errors)
-   [How to Fix Workday ACA 1095-C Code 2C Mismatches and Update Annual Affordability Thresholds](https://kiweely.com/guides/workday-aca-1095c-errors-affordability-setup)
-   [How to Reopen Workday Open Enrollment for One Employee After the Window Closes](https://kiweely.com/guides/workday-reopen-open-enrollment-single-worker)
-   [Why is a worker’s Workday Open Enrollment On Hold or missing after a backdated change?](https://kiweely.com/guides/workday-open-enrollment-stuck-disappeared-elections)
-   [How to Configure or Opt Out of the Modernized Workday Worker Profile and Private Tab](https://kiweely.com/guides/workday-worker-profile-header-private-public-tabs)
-   [How Future-Dated Dependents and ‘View Dependent As Of’ Work in Workday Benefits](https://kiweely.com/guides/workday-dependent-effective-dating-future-dependents)

### From the blog on More Workday guides

[All posts](https://kiweely.com/blog)

-   [The AGI Moment for the Workday Ecosystem](https://kiweely.com/blog/agi-moment-workday-ecosystem)
-   [Finding Workday Answers When Workday Community Search Comes Up Short](https://kiweely.com/blog/finding-workday-answers-beyond-workday-community)
-   [The Multi-Client Workday Consultant’s Guide to Zero Data Leakage in the AI Era](https://kiweely.com/blog/multi-client-consultant-zero-data-leakage)

## Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.
