A password is only one way to prove identity. Modern workplace authentication can require an additional factor, which is where Okta Verify enters the picture.
Okta defines Okta Verify as an MFA application that can confirm a user’s identity during sign-in to Okta-protected accounts and resources. Depending on organizational configuration, it can support mechanisms such as push approval, codes and device-based verification.
For Nordstrom-related searchers, this matters because a Nordstrom Okta Workday SAML endpoint is publicly visible. The existence of that connection makes Okta Verify a reasonable supporting topic without requiring us to invent Nordstrom-specific MFA rules that are not publicly documented.
The password worked. Why did the login stop?
Authentication often happens in stages. A username and password can establish one factor, while the system then requests another form of proof.
If the password is accepted but Okta Verify cannot complete the authentication, changing the password may not address the actual issue. The failure is occurring at another stage.
Okta’s own documentation explains that the app must be installed and set up on the device before it can be used for supported verification methods.
Why replacing a phone matters
A new phone is not necessarily the same enrolled authentication device simply because it has the same phone number or the same applications installed.
Okta provides specific procedures for setting up Okta Verify and adding accounts to devices. It also documents methods for moving an existing account to another supported device in certain configurations.
The important lesson is that employee authentication enrollment is more specific than “download the app again.” Organizational policy determines which options are available.
If setup cannot be completed, Okta’s documentation tells users to contact the organization’s IT administrator or help desk.
Push notification, code or another method?
Okta Verify supports multiple authentication experiences, but the organization controls which methods are presented. Okta documentation describes push notifications and time-based codes among the available experiences on supported devices.
An independent Nordstrom guide should therefore avoid promising a particular screen. “You will always receive a push” would be too specific. A better explanation is that the employee should follow the method offered by the approved company sign-in environment.
Security rule worth remembering
Never approve an authentication request you did not initiate. Okta explicitly advises users to reject unexpected sign-in attempts.
That point is more useful than reproducing a fake employee-login form on an informational website. Authentication belongs with the organization; an independent guide should help users understand what they are seeing.