Skip to content

Commit 223cb42

Browse files
committed
docs(fix): rm typos
1 parent 5b45d6b commit 223cb42

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

pages/audit-trail/reference-content/iam-authentication-logs.mdx

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ dates:
1010
This page explains how to differentiate IAM member authentication methods and understand and how they appear in Audit Trail.
1111

1212

13-
## 1. Authentication code login
13+
## Authentication code login
1414

1515
This flow allows a user to log in using an **authentication code** sent via email.
1616

@@ -23,7 +23,7 @@ This flow allows a user to log in using an **authentication code** sent via emai
2323
If multifactor authentication (MFA) is required, the flow proceeds to `CheckLoginMFAOTP`. Otherwise, the flow redirects to `CommitLogin`.
2424

2525

26-
## 2. Password login
26+
## Password login
2727

2828
This is the standard login method using a username and password.
2929

@@ -34,7 +34,7 @@ If MFA is required, the system verifies it through `CheckLoginMFAOTP`. If not, t
3434

3535

3636

37-
## 3. OAuth2 login
37+
## OAuth2 login
3838

3939
This flow is based on external OAuth2 authentication providers.
4040

@@ -47,7 +47,7 @@ This flow is based on external OAuth2 authentication providers.
4747
As with the other methods, if MFA is required, `CheckLoginMFAOTP` is triggered before committing the login. Otherwise, the flow continues to `CommitLogin`.
4848

4949

50-
## 4. SAML login
50+
## SAML login
5151

5252
This flow integrates with **SAML (Security Assertion Markup Language)** for Single Sign-On (SSO).
5353
It allows you to set up identity federation on your Organization and provide your teams with secure access to their via an Identity Provider (IdP).

0 commit comments

Comments
 (0)