Skip to content
KiweelyKiweelyKiweely

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
  • Applies to Workday SSO & Authentication
  • 5 min read
  • Published
  • By Kiweely
On this page

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

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) 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):

  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 (coming next for Claude, ChatGPT, and Gemini) or Kiweely 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

Related guides

All guides

Let Workday check the work.

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

Get the next guide in your inbox.

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

We’ll email you once to confirm. Unsubscribe in one click from any issue.