---
title: "Face ID & Fingerprint Unlock with Workday SSO on Mobile"
description: "How deskless workers complete corporate Workday SSO once on mobile and unlock with Face ID or fingerprint on later shifts while honoring token expiry."
url: https://kiweely.com/blog/biometric-face-id-fingerprint-reauth-for-workday-mobile-apps
---

# Using Face ID and Fingerprint Unlock with Workday Single Sign-On for Deskless Workers

Typing a 14-character corporate SSO password and SMS MFA code in a parking lot kills frontline mobile adoption. Pairing one-time Workday OAuth 2.0 Authorization Code + PKCE sign-in with hardware-backed Face ID or fingerprint unlock keeps shifts fast and security strict.

-   By Kiweely
-   November 15
-   6 min read

Nothing kills frontline Workday adoption faster than forcing an hourly warehouse, retail, or hospital worker to type a 16-character corporate email address, a rotating SSO password, and an authenticator code every time they want to check Friday’s payslip or request a sick day. Completing corporate **Workday Single Sign-On** once via OAuth 2.0 with PKCE—and gating subsequent shift opens behind hardware-backed **Face ID** or **fingerprint** unlock inside the **Kiweely Leaf** phone app—cuts sign-in to under one second while preserving every Workday token expiry, IP policy, and instant termination cutoff.

Desk workers sign in to Okta or Microsoft Entra ID once at 8:30 AM on a company-managed MacBook and ride browser session cookies all day. Deskless workers do not have company laptops; their personal iPhone or Android phone *is* their self-service terminal, and every unnecessary password prompt turns a 20-second schedule check into a forgotten-password call to the IT helpdesk.

## Why Browser Bookmark SSO Loops Frustrate Hourly Workers on Phones

When companies tell hourly workers to “just bookmark the Workday URL in mobile Safari or Chrome,” three authentication realities collide on the shop floor:

1.  **Aggressive Mobile Browser Session Timeouts:** Security teams rightly keep Workday browser session timeouts short (`Edit Tenant Setup - Security`, often 15–30 minutes of inactivity). Every time a worker opens a mobile browser tab two days later, the SAML session is gone, kicking off a multi-redirect bounce across Workday, Microsoft Entra ID or Okta, and an MFA prompt.
2.  **No Corporate Email Inbox on the Phone:** Many hourly associates do not have Exchange or Gmail installed on their personal phones, so email-based magic links or password-reset loops stall at shift change.
3.  **BYOD Resistance to Full MDM Profiles:** Workers are happy to download a normal App Store or Google Play app to view their pay stub and swap shifts, but they overwhelmingly refuse to install a corporate Mobile Device Management (MDM) device-admin profile that grants their employer wipe or inspection rights over personal photos and messages.

## How One-Time Workday OAuth + Biometric Re-Authentication Works End to End

A clean mobile security architecture separates **identity proofing** (handled by your Identity Provider and Workday OAuth 2.0) from **local presence verification** (handled by the phone’s biometric hardware) and **data residency** (zero HR records persisted on the phone or intermediary servers).

Here is the exact lifecycle when an employee uses Workday SSO with Face ID or fingerprint unlock:

| Lifecycle Step | What Happens on the Phone & Network | Security Boundary Enforced |
| --- | --- | --- |
|  **1\. First-Time Sign-In** | Worker opens the app, enters their company workspace code or email domain, and completes corporate SSO + MFA inside a system browser session (`ASWebAuthenticationSession` / Chrome Custom Tabs) against Workday’s OAuth 2.0 `Authorize` endpoint with **PKCE** (`S256`). | App never sees the worker’s password or MFA secret; [PKCE prevents authorization code interception](https://kiweely.com/guides/workday-api-client-pkce-sso-without-workday-password). |
|  **2\. Hardware-Gated Token Sealing** | Workday issues a short-lived user-delegated `Bearer` access token and a bounded refresh token (`Register API Client`). Credentials are sealed in the iOS Keychain (`SecAccessControl` with `.biometryCurrentSet`) or Android Keystore (`setUserAuthenticationRequired(true)`), never in `localStorage` or plaintext SQLite. | Enrolling a new fingerprint or face on the device invalidates `.biometryCurrentSet` automatically. |
|  **3\. Subsequent Shift Opens (< 1 sec)** | Worker taps the app icon or a push notification -> iOS Face ID / Touch ID or Android BiometricPrompt verifies the worker -> hardware releases the credential -> if the short-lived access token expired, the app exchanges the refresh token over TLS for a fresh access token. | A coworker or family member picking up an unlocked phone on a breakroom table still cannot open HR screens without the worker’s face or thumb. |
|  **4\. Live Pass-Through Workday Calls** | Screens fetch balances (`absenceManagement/v5`), clock hours (`timeTracking/v7`), or payslips live into volatile RAM. When the app closes or backgrounds, screen state clears—zero payslips or balances sit cached on flash storage. | Zero HR data at rest on the personal device eliminates BYOD data-leak exposure if a phone is lost. |
|  **5\. Expiry, Rotation, or Termination** | When [Workday’s configured refresh token TTL](https://kiweely.com/guides/workday-oauth-refresh-token-expiration-rotation-revocation) elapses, an admin runs token revocation, or HR processes a **Terminate Employee** event that disables the Workday Account, Workday immediately returns `401` / `invalid_grant`. | Access cuts off at the Workday tenant instantly—local Face ID success grants zero offline data access. |

## What Workday Administrators Control on `Register API Client`

Because biometric unlock wraps a standard Workday OAuth 2.0 **Authorization Code Grant** client (`Register API Client`), your Workday Security Administrator retains complete server-side governance inside the tenant without writing custom mobile code:

-   **Access Token Timeout (`Access Token Timeout (in minutes)`):** Keep access tokens short (for example, `15` to `60` minutes) so every new shift session validates live account status against Workday’s token endpoint.
-   **Refresh Token Timeout (`Refresh Token Timeout (in days)`):** Align re-authentication cadence with your CISO’s mobile policy—for instance, `30` or `90` days—so workers complete full corporate SSO + MFA once a month or once a quarter while enjoying 1-second Face ID unlock on every shift in between.
-   **Least-Privilege Functional Areas (`Scope`):** Grant the API client only the Functional Areas your mobile screens use (such as *Time Off and Leave*, *Time Tracking*, *Staffing*, and *Personal Data*). Even with a valid token, an endpoint outside those scopes returns `403 Forbidden`.
-   **Automatic Termination Cutoff:** Unlike shared Integration System Users, user-delegated OAuth tokens are bound to the individual worker’s `Workday Account`. Disabling the account or [revoking OAuth tokens on termination or transfer](https://kiweely.com/guides/workday-revoke-oauth-tokens-terminated-transferred-workers) severs access immediately across every device.

## Privacy-Safe Push Notifications on Personal Phones

Deskless workers miss manager comments, shift approvals, and onboarding deadlines because they do not check corporate email. Yet pushing detailed HR text onto a phone lock screen (*“Your Paid Sick Leave request for 8 hours on Friday was denied: medical note required”*) creates an obvious privacy violation on a breakroom table.

Pairing biometric unlock with **opaque, zero-PII push notifications** solves both halves:

1.  The lock-screen banner says only: **“You have an update waiting in your company workspace.”** No salary figures, absence types, medical reasons, or worker IDs ever traverse Apple Push Notification service (APNs) or Firebase Cloud Messaging (FCM).
2.  Tapping the banner triggers Face ID or fingerprint verification, exchanges/uses the worker’s live Workday OAuth token, and fetches the actual decision directly from Workday into memory.

## How the Kiweely Leaf Phone App Works for Your Workforce

Building, signing, security-auditing, and maintaining your own native iOS and Android Workday wrapper—complete with Keychain/Keystore biometric bindings, PKCE flows, and semi-annual App Store and Google Play compliance reviews—is a heavy distraction for an HRIS or internal IT team.

**[Kiweely Leaf](https://kiweely.com/leaf)** (**coming next**) removes that burden with one shared workforce app and a stateless pass-through architecture:

-   **Install Once from the App Store or Google Play:** Employees download **Kiweely Leaf** on iPhone or Android; nothing custom of yours ever waits in an Apple or Google store review queue. (Note: employees use **Kiweely Leaf**, whereas Workday consultants and admins use the separate **Kiweely** companion app at `/phone` for [Kiweely Vine](https://kiweely.com/vine) and [Kiweely Nest](https://kiweely.com/nest).)
-   **Workday SSO Once, Face ID or Fingerprint Thereafter:** Each worker signs in once through your corporate Workday SSO, unlocks with a face or fingerprint on future shifts, and lands directly in your company’s branded space—with your name, colors, [three-button frontline screens](https://kiweely.com/blog/simplifying-workday-for-frontline-warehouse-retail-healthcare), and any web apps your own developers host.
-   **Zero HR Data at Rest:** Neither the phone’s disk nor Kiweely’s servers store employee HR records at rest; every read and write executes live under the signed-in employee’s own Workday OAuth token, without requiring a Workday Extend license.

## Frequently asked questions

### Does biometric unlock bypass our corporate Okta, Microsoft Entra ID, or Ping single sign-on policy?

No. On initial sign-in (and whenever the Workday refresh token expires or is revoked), the worker authenticates directly through your corporate SAML/OIDC Identity Provider and Workday OAuth 2.0 Authorization Code flow with PKCE. Face ID or Android BiometricPrompt simply unlocks the hardware-protected keychain entry locally on the device.

### What happens immediately if a frontline employee leaves the company or is terminated in Workday?

Even if Face ID succeeds locally on the worker's phone, every screen load calls Workday live with that worker's OAuth token. Once Workday inactivates the Workday Account or revokes the token upon termination, Workday rejects the API call immediately and zero cached HR data exists on the device or server to view.

### Does Kiweely store the worker's Workday password or biometric template?

Never. Passwords and MFA stay strictly between the worker and your corporate SSO provider, and Face ID or fingerprint verification happens entirely inside the iOS Secure Enclave or Android StrongBox/Keystore hardware—biometric data never leaves the phone.

### Do we have to enroll personal hourly workers' phones into corporate MDM just to let them check pay and request time off?

No. When the mobile app holds zero HR records at rest on the phone and enforces biometric gating before unsealing short-lived OAuth credentials in memory, IT avoids invasive BYOD MDM profiles that hourly workers refuse to install.

## Read next

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

-   [November 15 ### Pass-Through Workday Screens vs. Caching HR Portals: Security and Sync Tradeoffs](https://kiweely.com/blog/pass-through-workday-ui-vs-caching-hr-portals)
-   [November 15 ### Five Things to Check in Your Workday Sandbox Before Connecting External AI or Custom Screens](https://kiweely.com/blog/preparing-your-workday-sandbox-for-kiweely-bridge-and-leaf)
-   [November 15 ### Designing Privacy-Safe Mobile Push Notifications for Workday Approvals and Pay Updates](https://kiweely.com/blog/privacy-safe-push-notifications-for-workday-tasks-on-phones)

### More guides on Business processes and security

[All 27 guides](https://kiweely.com/guides#business-processes)

-   [Explain a Workday business process in plain language, then configure the rule](https://kiweely.com/guides/ai-workday-business-process-design-plain-language)
-   [Turn a requirements note into a Workday business process](https://kiweely.com/guides/ai-brd-to-workday-business-process-design)
-   [Benefits Life-Event Intake That Starts the Right Workday Process](https://kiweely.com/guides/benefits-life-event-intake-workday-business-process)
-   [How do I document Workday configuration and business processes from a live tenant?](https://kiweely.com/guides/document-workday-configuration-and-business-processes)
-   [How to Run Role-Boundary Security Tests Across Employee, Manager, and HR Partner Personas](https://kiweely.com/guides/workday-role-boundary-testing-employee-manager-hr-partner)
-   [Aligning Workday Session Timeouts with External OAuth Access Token Lifetimes](https://kiweely.com/guides/workday-anonymous-vs-authenticated-session-timeout-oauth)
-   [How Workday Terminations and Job Transfers Affect Active OAuth Grants](https://kiweely.com/guides/workday-revoke-oauth-tokens-terminated-transferred-workers)
-   [Configuring Workday Pre-Hire Security So New Employees Can Complete Tasks Before Day One](https://kiweely.com/guides/workday-pre-hire-onboarding-access-before-day-one-security)

## Your Workday work, done by AI.

Kiweely Vine is the AI agent that builds, deploys and tests Extend apps as real people, makes changes in any Workday task screen, answers from your real tenant and builds reports.

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

## Get the next one in your inbox.

One email a month for Workday teams: what’s changing in Workday and what to retest, one tip tried in a real tenant, and what’s new at Kiweely.
