Okta and Workday can appear during the same employee journey, but they solve different problems.
| Okta | Workday | |
|---|---|---|
| Primary role | Identity and access | Enterprise workforce application |
| Employee may encounter it when | Authenticating | Performing a Workday task |
| MFA connection | Okta Verify can confirm identity | May rely on employer authentication |
| Nordstrom evidence | Public Workday SAML route | Current job postings direct employees into Workday |
The Nordstrom-specific connection is not speculative: a Nordstrom Okta SAML endpoint associated with Workday is publicly discoverable. Nordstrom’s current job postings also instruct existing employees to use Workday for internal job applications.
Okta answers “who is this?”
Okta provides identity-management and authentication functionality. Its End-User Dashboard is designed to give users secure access to enterprise applications, and Okta Verify can provide an additional method of confirming identity.
Workday answers “what employee process are we doing?”
Workday is the application environment. Its own login guidance explains that users access employer accounts through the employer’s unique sign-in page rather than a generic Workday employee credential.
This division explains why a Nordstrom employee can “be trying to log into Workday” while technically passing through Okta first.
Why the distinction matters
Consider three failures.
If a password is rejected before access is established, troubleshoot authentication.
If identity verification succeeds but Workday never becomes available, examine the handoff or authorization.
If Workday is already open and a Workday function fails, the issue may sit inside the destination application.
Those are different situations even though a user might describe all of them as “Nordstrom login not working.”
The purpose of a comparison page is therefore not to repeat both product guides. It is to make the boundary between them clear.