← Course Home
Okta Certified Administrator · Part II

Security Enforcement

23% of Part II — the final and most policy-heavy use case.

Security Enforcement

Task 1: Set Up an Authenticator

5 tasks · this deck covers task 1 of 5

↑ Security Enforcement Overview

The Task

"Set up an authenticator"

This exact concept already has a full deck — built for Part I's Security section. Here it's the same facts, just framed as something to actually click through.

The Connection — Full Deck Already Exists

That deck covers the 3 factor categories, the 5 method properties, the 15+ authenticator options, and Okta Verify's specific setup requirements (enrollment policy, OIE-only desktop support, Windows Autopilot incompatibility).

The Operational Angle

Setting one up, in practice: Security > Authenticators, add the authenticator tile, then set its enrollment policy to Optional or Required. That single setting is what actually determines whether users are forced to enroll or simply offered the option.

The Angle — What Trips People Up

Watch for this in your own sandbox run:

→ Adding an authenticator but leaving it effectively unused because the enrollment policy wasn't set to Required where it needed to be.

One Line To Remember

Setting up an authenticator = Security > Authenticators > add it > set enrollment policy to Optional or Required. Full conceptual background (factor categories, method properties, Okta Verify specifics) already lives in Security Module 1, Sub 1 — go there for the deep dive.

Sources: help.okta.com — about-authenticators.htm (full deck: Security Module 1, Sub 1)