Oracle’s September 25, 2026 announcement describes support for FIDO2 discoverable credentials in OCI IAM, enabling a sign-in flow that does not begin with a typed username or password. The announcement includes approved hardware security keys as an enrollment option, alongside built-in device authenticators. It is not a compatibility certification for every FIDO2 key or every Oracle service. Oracle’s announcement

For organizations evaluating passwordless access, the interesting change is the first interaction. Instead of asking employees to remember which identifier belongs in a login field, a service can let them select an eligible credential and complete the required verification.

What is a discoverable credential?

In WebAuthn terminology, a discoverable credential can be used when the service has not supplied a list of credential identifiers. The client-side authentication system can locate a credential for the service, allowing authentication to begin without the service first identifying the user. Older documentation may call this a resident key. W3C WebAuthn specification

“Discoverable” does not mean publicly searchable. It describes how the authentication system finds the appropriate credential during sign-in. It also does not eliminate the account behind that credential.

A useful way to explain the experience to employees is: choose your saved account credential, then complete the verification your device requests. That wording avoids suggesting that a single click always completes every step.

What Oracle announced—and what it did not

Oracle describes a passkey entry point followed by platform selection and verification. Its guidance calls for enabling FIDO2 and passkey authentication, enabling discoverable credentials, and requiring user verification. It also says exact administrative steps depend on the service and deployment. Oracle’s deployment outline

The announcement’s “one-click” description is best understood as a simpler entry point, rather than evidence that verification or organizational policy disappears.

For scope, Oracle’s IAM documentation explains that identity domains hold user populations and associated security configuration. Sign-on policies determine the criteria for allowing access to a domain. OCI IAM overview

Our recommendation is to document the specific identity domain, application, and user group being evaluated. A broad statement that “Oracle supports passkeys” is less useful to a deployment team than a named, tested sign-in journey.

Where FIDO2 hardware security keys fit

The FIDO Alliance describes passkeys as credentials that can be stored on phones, computers, or hardware security keys. A passkey is the credential; the security key is one possible authenticator that uses it. FIDO Alliance passkey overview

This distinction matters when purchasing hardware. Our recommended acceptance criteria include discoverable-credential support, a supported verification method, suitable connections for the intended endpoints, and acceptance under the organization’s identity policies. Ask for current documentation for the exact model rather than inferring these details from a family name.

Also decide where the credential should live. An employee following a registration prompt should understand whether they are using an approved physical key or a different credential provider. That is an onboarding question worth answering before rollout.

Test account selection, not just successful login

A username-free entry point changes the experience enough to deserve its own pilot. We recommend testing with a small set of representative users and devices before broad enforcement.

Start with one eligible account and a newly registered credential. Then test the situations most likely to confuse the intended users:

  • A person has both a standard account and an administrative account.
  • The same workstation is used by different people during the day.
  • A user cancels credential selection and starts again.
  • The primary authenticator is unavailable and the approved alternative must be used.
  • The application is reopened after a previous session has ended.

For each case, confirm the account actually opened, the verification requested, and the outcome after cancellation or sign-out. Keep the pilot record free of private keys, recovery codes, or other authentication secrets.

This checklist is our editorial recommendation, not a report of testing conducted by Thetis. Its purpose is to expose ambiguous account choices before they become repeated support tickets.

Measure usability without overstating security

A rollout can be evaluated with practical measures: completed sign-ins, account-selection errors, time spent obtaining help, and successful use of an approved alternative. Establish a baseline before making claims about improvement.

Avoid treating a shorter login form as proof that all account risks have been addressed. Authentication, session handling, and account administration are separate parts of a working deployment. Assign an owner to each part and make the escalation path clear.

For teams considering physical authenticators, explore Thetis FIDO2 security keys and check the chosen model against the actual OCI IAM configuration. No Thetis-specific interoperability result is claimed here.

Oracle’s update is a useful prompt to reconsider the beginning of the sign-in journey. The strongest outcome is a process in which users can identify the right account, complete the required verification, and recover from ordinary mistakes without uncertainty.

Recent platform update: announcement published September 25, 2026; reviewed October 1, 2026. Pilot suggestions are editorial recommendations.