> For the complete documentation index, see [llms.txt](https://docs.openiam.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openiam.com/getting-started-guide/authentication.md).

# Authentication and self-service

How content providers, authentication providers, policies, and rules fit together.

Five objects govern who gets prompted for what. Two minutes here saves an hour of clicking.

| Object                      | What it owns                                                                                                   | Where (Webconsole)                        |
| --------------------------- | -------------------------------------------------------------------------------------------------------------- | ----------------------------------------- |
| **Content provider**        | A served domain: URL patterns, theme, and which authentication provider applies                                | Access Control → Content Providers        |
| **Authentication provider** | *How* users authenticate: password, plus OTP channels (email/SMS), FIDO2, etc.                                 | Access Control → Authentication Providers |
| **Authentication policy**   | Lockout and token rules: failed-attempt count, auto-unlock time, token life                                    | Security → Authentication Policies        |
| **OTP provider**            | A delivery channel instance: Email Code, Twilio SMS, etc. Email OTP depends on a working mailbox configuration | Access Control → OTP Provider             |
| **Password policy**         | Composition, expiry, and the forgot-password/SSPR parameters                                                   | Policy → Password Policy                  |

If a menu item isn't where the table says, use the Webconsole search — the object names are stable even where menu grouping shifts between releases.

The chain for MFA on a URL: a **content provider** URL pattern carries an authentication-level rule (e.g. TOTP) → the linked **authentication provider** must support that method (e.g. email OTP enabled) → the **OTP provider** delivers the code → the **authentication policy** decides lockout behavior when it goes wrong.

## Prerequisites for both pages in this section

1. **SMTP first.** Email OTP, password-reset links, and most notifications all depend on **Administration → Mailbox Configurations**. Configure and test it before anything else (templates exist for Gmail, Office 365, SendGrid).
2. **Break-glass admin** ([Verify health and log in](/getting-started-guide/verify-and-first-login.md)). You are about to change login behavior; keep a second admin session open in another browser for every change in this section, and don't apply MFA rules to `/webconsole/*` until you've proven the flow on a harmless URL.
3. A **non-admin test user with a real mailbox** — ideally one imported from AD in the lifecycle POC. One catch: AD synchronization imports identities, **not passwords**. Before the user can log in to OpenIAM, set them an OpenIAM password with the admin *Change Password* action on their user record (delegated authentication against AD is a production option covered in the Administration Guide, not configured in this POC).

Start with [Require MFA for one URL](/getting-started-guide/authentication/mfa-for-one-url.md), then [Password policy and self-service reset](/getting-started-guide/authentication/password-policy-and-sspr.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.openiam.com/getting-started-guide/authentication.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.