trustchain-oc1-orchestral
/
authentik
Archived
10
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

website/docs: Added mention of how to force 2fa (#3497) 

* Added mention of how to force 2fa

Added mention of how to force 2fa and fixed some punctuation's.

Signed-off-by: Joeri Colman <colmanjoeri@msn.com>

* Update website/docs/flow/examples/flows.md

Co-authored-by: Jens L. <jens@beryju.org>
Signed-off-by: Joeri Colman <colmanjoeri@msn.com>

Signed-off-by: Joeri Colman <colmanjoeri@msn.com>
Co-authored-by: Jens L. <jens@beryju.org>
This commit is contained in:
Joeri Colman 2022-08-29 14:14:10 +02:00 committed by GitHub
parent d0b52812d5
commit a4556b3692
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
website/docs/flow/examples/flows.md
View File

@ -28,7 +28,9 @@ You'll probably have to adjust the Email stage and set your connection details.
Flow: right-click [here](/blueprints/example/flows-login-2fa.yaml) and save the file.
Login flow which follows the default pattern (username/email, then password), but also checks for the user's OTP token, if they have one configured
Login flow which follows the default pattern (username/email, then password), but also checks for the user's OTP token, if they have one configured.
You can force two-factor authentication by editing the *Not configured action* in the Authenticator Validation Stage.
## Login with conditional Captcha
@ -36,7 +38,7 @@ Flow: right-click [here](/blueprints/example/flows-login-conditional-captcha.yam
Login flow which conditionally shows the users a captcha, based on the reputation of their IP and Username.
By default, the captcha test keys are used. You can get a proper key [here](https://www.google.com/recaptcha/intro/v3.html)
By default, the captcha test keys are used. You can get a proper key [here](https://www.google.com/recaptcha/intro/v3.html).
## Recovery with email verification
@ -48,7 +50,7 @@ Recovery flow, the user is sent an email after they've identified themselves. Af
Flow: right-click [here](/blueprints/example/flows-unenrollment.yaml) and save the file.
Flow for users to delete their account,
Flow for users to delete their account.
:::warning
This is done without any warning.