---
title: "Workday Studio OAuth API Client with PKCE Auth — Kiweely"
description: "Register a Workday OAuth API Client with Authorization Code Grant and PKCE so Studio and external tools sign in when SSO removes Workday passwords."
url: https://kiweely.com/guides/workday-api-client-pkce-sso-without-workday-password
---

# How to Authenticate Workday Studio and External Tools Using an OAuth API Client with PKCE (When SSO Blocks Passwords)

When SSO leaves consultants without a Workday password, register an API Client with Authorization Code Grant and Support Proof Key for Code Exchange enabled, then use that client ID with Studio or Vine OAuth sign-in instead of username and password auth.

-   **Checked** against Workday on November 13
-   Applies to **Workday Studio**
-   4 min read
-   Published November 13
-   By Kiweely

When corporate SSO leaves a consultant without a Workday password, Workday Studio’s basic authentication path cannot sign in to that tenant. Register an OAuth **API Client** with **Authorization Code Grant** and **Support Proof Key for Code Exchange (PKCE)** enabled, then connect Studio (or another interactive tool) with that client ID and the authorization and token endpoints Workday displays after registration.

PKCE is the OAuth extension that proves the same public client that started the authorize request is the one redeeming the authorization code. Workday exposes it as a checkbox on **Register API Client**. You still authenticate as a person in the browser; you are not pasting long-lived passwords into Studio connection preferences.

## When Does Username and Password Auth Stop Working?

Use this decision table before you rebuild Studio preferences:

| Sign-in Situation | What Works | What Fails |
| --- | --- | --- |
| Account has a Workday password (and MFA if enrolled) | Studio basic authentication, or OAuth Authorization Code | Nothing inherent |
| Account is SSO-only with no Workday password | OAuth Authorization Code + PKCE API Client | Studio basic authentication that demands a Workday password |
| User enrolled in Workday MFA | OAuth browser flow prompts for the second factor | Expecting OAuth to skip MFA |
| Unattended ISU batch job | Dedicated integration API client patterns for non-interactive use | Reusing a person’s Authorization Code PKCE client for overnight jobs |

For Integration System User setup patterns (separate from this interactive Studio flow), see [ISU and API client setup](https://kiweely.com/guides/workday-integration-system-user-api-client) and [ISU authentication errors](https://kiweely.com/guides/workday-isu-authentication-errors).

## How Do You Register the API Client Correctly?

Workday’s Studio multifactor topic documents the client settings Interactive Studio needs. Access **Register API Client** (security administrators typically hold **Security Administration** in the System functional area) and configure:

| Option | Value for Studio-style interactive OAuth |
| --- | --- |
| Client Grant Type | Authorization Code Grant (Authorization Grant Code) |
| Support Proof Key for Code Exchange (PKCE) | Enabled / selected |
| Access Token Type | Bearer |
| Redirection URI | An HTTPS URI your organization provides for the callback |
| Scope (Functional Areas) | Every functional area for the web services you will call, plus Implementation, Integration, System, and Tenant Non-Configurable when following the Studio guidance |
| Include Workday Owned Scope | Enabled when required by the Studio topic |

Related Workday examples (Time Kiosk registration) also select Authorization Code Grant, enable PKCE, and use Bearer access tokens. Those examples prove the same checkbox and grant type pattern across products.

After you click OK, copy the **Client ID**, **Authorization Endpoint**, and **Token Endpoint** from the confirmation page. Store the confidential client material your tenant shows in your organization’s secret manager. Do not embed those values in shared chat logs or public docs.

Access token lifetime

The Studio MFA topic warns not to select **Enforce 60 Minute Access Token Expiry** on this client style, because that setting disables OAuth authentication after that period. OAuth sessions also follow normal Workday session timeouts configured tenant-wide or per account.

## How Do You Connect Workday Studio With the Client?

On the machine that runs Studio:

1.  Open **Preferences**, then **Workday** → **Connections**.
2.  Add (or edit) the tenant connection.
3.  Open the **OAuth 2.0 credentials** tab.
4.  Paste the Client ID, Authorization Endpoint, and Token Endpoint from **Register API Client**.
5.  Start **Get Access Token**. Workday opens the authorize flow; complete corporate SSO (and MFA if enrolled).
6.  Test the connection, then apply and close.

If Studio returns an internal server error at token retrieval, the Studio topic cites an incorrect Client ID as the most common cause. Confirm you registered in the same tenant you are connecting, and that PKCE remained enabled on that client.

Fails

```
# Anti-pattern when SSO removed Workday passwords
1. Keep Studio on basic authentication
2. Paste a personal password into connection preferences
3. Fail when the account has no Workday password, or rotate passwords break every laptop
```

Works

```
# Documented interactive path
1. Register API Client with Authorization Code Grant + PKCE
2. Scope the functional areas Studio will call
3. Paste Client ID + authorize/token endpoints into Studio OAuth tab
4. Complete browser SSO (and MFA) once per session renewal
```

## How Do External Desktop Tools Fit (Including Vine)?

Any interactive tool that implements Authorization Code with PKCE against Workday’s authorize and token endpoints can use the same client style, provided its redirect URI is listed on the API Client and reachable over HTTPS. [Kiweely Vine](https://kiweely.com/vine) supports Workday sign-in with saved credentials, username and password connections, and OAuth API client with PKCE for tenants where SSO leaves no Workday password for Studio-style work. Keep each client’s tenants isolated; do not reuse one engagement’s API Client on another customer’s laptop image.

For Postman-style API exploration after you have an interactive session, see [Workday API token setup for Postman](https://kiweely.com/guides/workday-api-token-postman). For deployment and runtime failures after sign-in succeeds, return to [Debug Workday Studio integrations](https://kiweely.com/guides/debug-workday-studio-integration).

## What Proves Sign-In Is Fixed?

1.  Studio (or Vine) connects to the target tenant without prompting for a Workday password the account does not have.
2.  The authorize browser page completes SSO for the intended person.
3.  MFA challenges still appear when the person is enrolled.
4.  A simple secured call (for example opening an integration system the person can view) succeeds under the new connection.
5.  The API Client scopes include every functional area for the web services the assembly actually calls; missing scopes fail later as authorization errors, not as “wrong password” errors.

Register the client once per tenant purpose, rotate it when people leave the engagement, and keep interactive PKCE clients separate from unattended integration credentials.

## Frequently asked questions

### Why does Workday Studio fail when the tenant uses corporate SSO only?

Studio basic authentication expects a Workday username with a Workday password. When identity is federated and the account has no Workday password, that path cannot complete. Register an API Client with Authorization Code Grant and PKCE, then connect Studio through the OAuth credentials tab instead.

### Which API Client grant type should I select for Studio interactive sign-in?

Use Authorization Code Grant (also labeled Authorization Grant Code in the Studio MFA topic), enable Support Proof Key for Code Exchange, set Access Token Type to Bearer, and supply an HTTPS redirection URI your organization controls.

### Do I still need multifactor authentication after switching Studio to OAuth?

If the user is enrolled in Workday multifactor authentication, Workday still prompts for the second factor during the OAuth browser sign-in. OAuth replaces password-based Studio login; it does not bypass MFA enrollment rules.

### Should integration system users use the same Authorization Code PKCE client?

No. Interactive Studio and desktop tools use Authorization Code Grant with PKCE for a person signing in. Unattended integrations typically use a dedicated Integration System User with a separate API client pattern suited to non-interactive calls. Keep person sign-in clients and integration clients separate.

## Sources checked

-   [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)
-   [Register API Clients (OAuth)](https://doc.workday.com/admin-guide/en-us/authentication-and-security/authentication/oauth/dan1370797831010.html)
-   [Register API Clients for Integrations](https://doc.workday.com/admin-guide/en-us/authentication-and-security/authentication/oauth/dan1370797831458.html)
-   [Register API Clients for Time Kiosks (PKCE checkbox example)](https://doc.workday.com/admin-guide/en-us/human-capital-management/time-tracking/time-entry-setup/time-kiosk/register-api-clients-for-time-kiosks.html)

## Related guides

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

-   [### How to Fix Workday Studio SDKProfile Not Current and Unsigned Software Startup Errors on Mac and Windows Workday Studio throws Profile SDKProfile is not current when Eclipse p2 metadata gets out of sync after an interrupted update or read-only install path, while unsigned warnings stem from macOS quarantine attributes or Eclipse plugin trust prompts. Clear quarantine or reinstall cleanly.](https://kiweely.com/guides/workday-studio-sdkprofile-not-current-unsigned-macos-errors)
-   [### How to get a Workday API access token in Postman For a tenant-registered API client, generate a refresh token for an integration system user, then POST grant\_type=refresh\_token to the token endpoint shown on the client, with the client ID and secret as Basic auth. For a Developer Site client, use Postman’s OAuth 2.0 authorization code flow.](https://kiweely.com/guides/workday-api-token-postman)
-   [### How to Debug a Failing Workday Studio Integration, Step by Step When a Workday Studio integration fails, the error message alone rarely tells you enough. This guide walks through a structured debugging process: reading Integration Events, isolating the failing step, using Studio’s breakpoint and message-inspection tools, and resolving common error patterns.](https://kiweely.com/guides/debug-workday-studio-integration)
-   [### Workday ISU or API client 401, invalid\_client, invalid\_grant These errors usually blame the token, but the real cause is the ISU’s own account, its security group’s activation, or the wrong client task — not a corrupted credential.](https://kiweely.com/guides/workday-isu-authentication-errors)
-   [### How do I set up an integration system user and API client in Workday so an external app can authenticate? Create the ISU, put it in an Integration System Security Group, grant domain permissions and activate them, register the client for integrations, then generate its refresh token and pick the ISU as the Workday account.](https://kiweely.com/guides/workday-integration-system-user-api-client)

### More guides on Integrations and APIs

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

-   [Workday PECI vs. PICOF Payroll Connectors: How Effective-Dated Stack and Retro Changes Export](https://kiweely.com/guides/workday-peci-picof-payroll-connector-change-detection)
-   [Why does my Workday Accounting Journal EIB fail? Balancing, worktag and period errors](https://kiweely.com/guides/workday-financials-accounting-journal-eib-validation-errors)
-   [How to Find Every Domain and Web Service Permission an ISU Needs in Workday (Without Guesswork)](https://kiweely.com/guides/workday-isu-permissions-activate-pending-security-policy-changes)
-   [How to Fix The Load Contains a Duplicate Key and Invalid Reference ID Errors in Workday EIB](https://kiweely.com/guides/workday-eib-duplicate-key-reference-id-errors)
-   [How to Troubleshoot Workday Cloud Connect for Benefits (CCB) and Missing Dependents on 834 Feeds](https://kiweely.com/guides/workday-cloud-connect-for-benefits-834-errors)
-   [Why Workday Scheduled Reports and Integrations Shifted Dates After Local Time Zone Processing](https://kiweely.com/guides/workday-local-time-zone-processing-report-integration-impacts)
-   [Workday Mass Job Change Tables vs. Change Job EIB: Limits, Security, and When to Use Each](https://kiweely.com/guides/workday-mass-job-change-vs-eib)
-   [Workday Data Cloud vs. EIB, RaaS, and Prism: Which Data Path Should You Use?](https://kiweely.com/guides/workday-data-cloud-vs-eib-raas-prism)

### From the blog on Integrations and APIs

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

-   [How an admin sets up the Workday API client for Kiweely Bridge](https://kiweely.com/blog/kiweely-bridge-ai-admin-api-client-setup)
-   [AI-Maintained Benefits Feeds and Hand-Owned Cloud Connect Maps](https://kiweely.com/blog/maintained-benefits-feeds-versus-hand-owned-cloud-connect-maps)
-   [Ask Claude, ChatGPT, or Gemini About a Failed Workday Run](https://kiweely.com/blog/ask-an-assistant-about-a-failed-workday-integration)

## 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.
