---
title: "Fix SSO Redirect Loops on Workday OAuth Authorize URL"
description: "Fix SAML and OIDC identity provider redirect loops, Login Redirect URL traps, and Authentication Policy routing failures on the Workday OAuth Authorize…"
url: https://kiweely.com/guides/workday-sso-saml-oidc-loop-external-oauth-authorize-endpoint
---

# Resolving SSO Redirect Loops on the Workday OAuth Authorize Endpoint

Break SAML and OIDC redirect loops on Workday’s OAuth Authorize Endpoint by fixing IdP-initiated Login Redirect URLs in Edit Tenant Setup - Security, aligning SP-initiated SAML settings, and adding OAuth 2.0 to your Manage Authentication Policies rules.

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

SSO redirect loops on Workday’s OAuth 2.0 **Authorization Endpoint** (`/<tenant>/authorize`) happen when Workday forwards an unauthenticated employee to your SAML or OpenID Connect identity provider, the IdP posts back to Workday without preserving the OAuth `RelayState` (or Workday rejects the assertion), and Workday bounces the browser back to the IdP again. Fixing the loop requires aligning three tenant settings: **SP-initiated SAML Redirection URLs** on **Edit Tenant Setup - Security**, environment flags on your SAML IdP row, and **Allowed Authentication Types** in **Manage Authentication Policies**.

## Symptom-to-Cause Diagnostic Matrix

Observe where the browser stalls or lands in your DevTools Network trace (`Preserve log` checked) to pinpoint which of the five failure modes is active:

| Observed Browser Symptom | HTTP / SAML Trace Signature | Root Cause in Workday |
| --- | --- | --- |
|  **User signs in at IdP and lands on the Workday Home page; external app never receives `?code=`** | `/authorize` -> `302` to static IdP chicklet URL -> `POST` SAMLResponse with empty/home `RelayState` -> Workday UI |  **Login Redirect URL** uses IdP-initiated SSO URL instead of SP-initiated `login-saml2.htmld`, dropping the OAuth context. |
|  **Infinite `302` bounce between Workday and Okta / Microsoft Entra ID / Ping (`ERR_TOO_MANY_REDIRECTS`)** | `/authorize` -> IdP -> `POST` SAMLResponse -> Workday rejects assertion -> `302` back to `Login Redirect URL` | Clock skew, expired X.509 certificate, wrong **Issuer** or **Used for Environments** flag in SAML Setup, or user lacks SSO permission in **Manage Authentication Policies**. |
|  **Works on laptop browser, loops or shows native password box on iPhone / Android** | Mobile User-Agent hits `/authorize` -> different redirect target than desktop |  **Mobile Browser Login Redirect URL** is misconfigured or blank on **Edit Tenant Setup - Security** or the **Authentication Selector**. |
|  **Sandbox Preview or Implementation loops after tenant refresh** | SAML request carries Production `Service Provider ID` or routes to Prod IdP ACS URL | Missing **Preview Only** redirect URL row or **Used for Environments** mismatch on the SAML Identity Provider grid. |
|  **User picks an IdP on Workday’s selector screen, then loops back to the selector** | Multi-IdP tenant using **Authentication Selector** |  **Redirect Type** is set to `Authentication Selector`, but the chosen selector entry points to an IdP-initiated URL or disabled IdP. |

## Cause 1: IdP-Initiated `Login Redirect URL` Dropping OAuth `RelayState`

When an external application sends an employee to Workday’s **Authorization Endpoint** ([configured via Register API Client](https://kiweely.com/guides/workday-authorization-code-grant-user-delegated-oauth-setup)):

Works

```
GET /gms/authorize?response_type=code&client_id=ODQ4ZDdkNzItMzhiMC00YmFmLTgyNzAtNzljNjM0MDlmNmY2&redirect_uri=https%3A%2F%2Fportal.company.example%2Foauth%2Fcallback&state=xyz987&code_challenge=E9Melhoa2OwvFrEMTJguCHaoeK1t8URWbuGJSstw-cM&code_challenge_method=S256 HTTP/1.1
Host: wd3.workday-host.example
```

If the employee does not already hold an active Workday session cookie in that browser, Workday checks the **Redirection URLs** grid on **Edit Tenant Setup - Security** (under **Single Sign-On**).

-   **Broken setup (IdP-initiated URL):** If **Login Redirect URL** (or **Mobile Browser Login Redirect URL**) is hardcoded to an IdP-initiated launch URL (such as an Okta app embed link that starts a brand-new SAML assertion with no incoming `SAMLRequest`), the IdP authenticates the user and drops them onto the default Workday landing page—completely forgetting the `/authorize` transaction and `redirect_uri`!
-   **Correct setup (SP-initiated SAML):** Configure **SP Initiated** on your SAML Identity Provider row in **Edit Tenant Setup - Security** (populating **Service Provider ID**, **IdP SSO Service URL**, and **SHA256** signature settings) and set **Login Redirect URL** and **Mobile Browser Login Redirect URL** to Workday’s SP-initiated endpoint for that tenant:

text

```
https://<workday-host>/<tenant>/login-saml2.htmld
```

With SP-initiated SAML active, Workday issues a signed `AuthnRequest` alongside a `RelayState` token referencing the pending OAuth `/authorize` parameters. As soon as the IdP posts the signed `SAMLResponse` back to Workday, Workday resumes the OAuth flow and redirects `302 Found` to your external app’s `redirect_uri` with `?code=...&state=...`.

## Cause 2: Rejected SAML Assertions Triggering Infinite Bounces

When Workday *rejects* an incoming SAML assertion—while **Login Redirect URL** automatically sends unauthenticated browsers back to the IdP—and the user already has an active SSO cookie at the IdP, the browser bounces endlessly between Workday and the IdP until Chrome, Safari, or Edge aborts with `ERR_TOO_MANY_REDIRECTS`.

Break the mystery in under two minutes by running **Signons and Attempted Signons** (see [Auditing External API Calls in Workday Sign-On History](https://kiweely.com/guides/workday-view-api-client-audit-logs-sign-on-history)) for the affected worker’s username:

1.  **SAML `Issuer` or `Used for Environments` mismatch:** Open **Edit Tenant Setup - Security** -> **SAML Setup**. Workday validates a SAML assertion **only** if the incoming `Issuer` matches a configured IdP row **and** the current tenant environment (`Production`, `Sandbox`, `Implementation`, or **Preview Only**) is enabled on that row.
2.  **X.509 Certificate rotation or `Enable Signature KeyInfo Validation`:** If your IAM team rolled the IdP signing certificate in Entra ID or Okta without updating the **x509 Certificate** on the SAML IdP row in Workday, **Signons and Attempted Signons** logs a signature mismatch on every bounce.
3.  **Server clock skew:** Workday enforces a combined 3-minute maximum skew window around `NotBefore` / `NotOnOrAfter`. Check **Additional Negative Skew (in minutes)** and **Additional Positive Skew (in minutes)** on **Edit Tenant Setup - Security** if NTP drift triggers sporadic rejections.
4.  **Deflate compression:** Certain SAML IdPs fail to parse Workday’s default deflate-compressed SP-initiated `AuthnRequest`. Select **Do Not Deflate SP-initiated Request** on the SAML IdP row if your IdP rejects incoming requests from `login-saml2.htmld`.

## Cause 3: Authentication Policy Rules Blocking SSO or OAuth

Even when SAML succeeds at the cryptographic layer, **Manage Authentication Policies** determines which authentication types a worker’s security group may use from their current IP address ([IP range rules guide](https://kiweely.com/guides/workday-maintain-ip-ranges-manage-authentication-policies-api)):

1.  Open **Manage Authentication Policies** and locate the first rule matching the employee’s security group and network location.
2.  Confirm that the employee’s SSO method (`SAML` or `OpenID Connect`—note that Workday’s native OpenID Connect provider setting supports Google) **and** `OAuth 2.0` are permitted where required by your policy structure.
3.  If you edit any rule, run **Activate All Pending Authentication Policy Changes** immediately so the change goes live.

## Bypassing SSO Redirects in Sandbox (`redirect=n`)

During early Sandbox or Implementation testing—before IAM wires a non-production SAML IdP—consultants and admins who have native Workday passwords enabled in their Sandbox authentication policy can bypass the tenant’s **Login Redirect URL** on the Authorize Endpoint by appending `&redirect=n` (or signing in first via `login.htmld?redirect=n` in the same browser profile before hitting `/authorize`). Never rely on `redirect=n` for production workforce accounts governed by SSO-only policies.

## Pre-Rollout Verification Checklist

-   Test the `/authorize` flow in a **fresh Incognito / Private browser window** (no pre-existing Workday session cookie) on **both** a desktop browser and a mobile phone browser.
-   Confirm the browser travels: `External App -> Workday /authorize -> login-saml2.htmld -> Corporate IdP + MFA -> Workday ACS -> External App redirect_uri?code=...`.
-   Verify in **Signons and Attempted Signons** that zero failed sign-on rows precede the successful sign-in.

When organizations deploy [Kiweely Bridge](https://kiweely.com/bridge) (coming next for Claude, ChatGPT, and Gemini) or [Kiweely Leaf](https://kiweely.com/leaf) (coming next for custom web, chat, and mobile employee screens), employees complete SSO and MFA directly on Workday’s own sign-in screen—meaning Kiweely never sees a worker’s password or MFA factor, and clean SP-initiated SAML configuration benefits every external channel at once.

## Frequently asked questions

### Why does SAML SSO drop the OAuth client\_id and land the user on the Workday home page instead of redirecting back to our app?

Your tenant's Login Redirect URL in Edit Tenant Setup - Security points to an IdP-initiated SAML app tile URL instead of Workday's SP-initiated SAML endpoint (login-saml2.htmld). IdP-initiated login discards the RelayState carrying the OAuth /authorize request.

### Can I test an OAuth client natively in Sandbox when Sandbox lacks an IdP connection?

Yes, if your test account's Authentication Policy permits User Name Password in Sandbox, appending &redirect=n to the Authorization Endpoint bypasses the SSO Login Redirect URL and renders Workday's native login form.

### Why do mobile phones loop on the Authorize Endpoint while desktop browsers succeed?

Workday evaluates Mobile Browser Login Redirect URL separately from desktop Login Redirect URL in Edit Tenant Setup - Security (and Manage Authentication Selectors). Verify the mobile browser URL also uses SP-initiated SAML or proper RelayState.

### Does clock skew between Okta/Entra ID and Workday cause infinite SAML redirect loops?

Yes. If the IdP server clock drifts beyond NotBefore / NotOnOrAfter bounds, Workday rejects the SAML assertion, sees an unauthenticated user, and redirects right back to the IdP—creating an instant browser loop visible in Signons and Attempted Signons.

## Sources checked

-   [Workday Admin Guide — Reference: Edit Tenant Setup - Security](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/tenant-setup/dan1370796470031.html)
-   [Workday Admin Guide — Configure IdP-Initiated and SP-Initiated SAML Authentication](https://doc.workday.com/admin-guide/en-us/authentication-and-security/authentication/saml/tar1437415584435.html)
-   [Workday Admin Guide — Set Up Authentication Selectors](https://doc.workday.com/admin-guide/en-us/authentication-and-security/authentication/authentication-selectors/wil1464044340244.html)

## Related guides

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

-   [### Auditing External API Calls in Workday Sign-On History and Activity Logs Trace external Workday OAuth sign-ins and API requests using four native tools: Signons and Attempted Signons for auth events, View User Activity for 30-day read/write/download calls, View API Clients for client inventory, and View User or Task or Object Audit Trail for mutations.](https://kiweely.com/guides/workday-view-api-client-audit-logs-sign-on-history)
-   [### 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)
-   [### Restricting Workday OAuth Token Use by IP with Maintain IP Ranges Lock down external Workday OAuth 2.0 API traffic by defining CIDR allowlists in Maintain IP Ranges, binding authentication rules in Manage Authentication Policies, and running Activate All Pending Authentication Policy Changes without locking out administrators.](https://kiweely.com/guides/workday-maintain-ip-ranges-manage-authentication-policies-api)
-   [### 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)

-   [Managing Workday OAuth Refresh Token Expiration, Rotation, and Revocation](https://kiweely.com/guides/workday-oauth-refresh-token-expiration-rotation-revocation)
-   [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)

### From the blog on More Workday guides

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

-   [How to choose which AI model to use in kiweely](https://kiweely.com/blog/how-to-choose-which-model-to-use-in-kiweely)
-   [From intent to deployed app in one conversation](https://kiweely.com/blog/intent-to-deployed-app)
-   [Multi-client AI for Workday consultants: keeping your clients’ data separate](https://kiweely.com/blog/multi-client-data-separation)

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