Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: add a bit of language around dynamic MFA for SEO #1490

Merged
merged 1 commit into from
Aug 3, 2023
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/kratos/mfa/01_overview.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -19,7 +19,7 @@ By enabling two-factor authentication in your project, you introduce an addition
or self-service actions, such as updating account information or credentials, from malicious actors.
For example, you might decide to require a user to log in with two factors right at the start of the session. Alternatively, you
could allow the user to start the session by logging in with the first factor and only require the second factor at the point
where the user is about to perform a security-sensitive operation. Read more about this in the
where the user is about to perform a security-sensitive operation. Read more about dynamic MFA in the
[step-up authentication](https://www.ory.sh/docs/kratos/mfa/step-up-authentication) document.

## Available methods
Expand Down
17 changes: 9 additions & 8 deletions docs/kratos/mfa/05_step-up-authentication.mdx
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
id: step-up-authentication
title: Use step-up authentication to protect high-risk operations
sidebar_label: Step-up authentication
title: Use dynamic multi-factor (step-up) authentication to protect high-risk operations
sidebar_label: Dynamic Multi-Factor Authentication
---

# Step-up authentication
Expand All @@ -17,14 +17,14 @@ You can set up multi-factor authentication to work in one of two models:
- **Strict**, where secured operations always require the highest Authenticator Assurance Level (AAL).
- **Lax**, where the secured operations require only the `aal1` Authenticator Assurance Level (AAL).

In Ory Network, the default multi-factor authentication enforcement model is **Strict**. This means that high-risk operations via
self-service endpoints, such as updating user settings, require step-up authentication by default.

You can set the required authentication model for these operations/endpoints:

- User sign-in (getting an Ory Session) / `/sessions/whoami` endpoint
- Self-service user settings

In the Ory Network, the default multi-factor authentication enforcement model is **Strict**. This means that high-risk operations
such as updating user settings require step-up authentication by default.

## Configuration

```mdx-code-block
Expand Down Expand Up @@ -95,10 +95,11 @@ Follow these steps to adjust the settings in the Ory Network using the Ory CLI:
</Tabs>
```

## Trigger step-up authentication
## Trigger Dynamic Multi-Factor authentication

You can make users complete a second authentication factor in their current session by initiating a new login flow using one of
these endpoints with the `aal` parameter set to `aal2`:
To protect your application's sensitive functions - like accessing payment details, an order history, or private content - you can
make users complete a second authentication factor in their current session by initiating a new login flow using one of these
endpoints with the `aal` parameter set to `aal2`:

- [`/self-service/login/browser`](../../reference/api.mdx#operation/initializeSelfServiceLoginFlowForBrowsers)
- [`/self-service/login/api`](../../reference/api.mdx#operation/initializeSelfServiceLoginFlowWithoutBrowser)
Expand Down
Loading