89c84f10d0
* managed: move flowexporter to managed Signed-off-by: Jens Langhammer <jens.langhammer@beryju.org> * *: implement SerializerModel in all models Signed-off-by: Jens Langhammer <jens.langhammer@beryju.org> * managed: add initial api Signed-off-by: Jens Langhammer <jens.langhammer@beryju.org> * managed: start blueprint Signed-off-by: Jens Langhammer <jens.langhammer@beryju.org> * managed: spec Signed-off-by: Jens Langhammer <jens.langhammer@beryju.org> * version blueprint Signed-off-by: Jens Langhammer <jens.langhammer@beryju.org> * yep Signed-off-by: Jens Langhammer <jens.langhammer@beryju.org> * remove v2, improve v1 Signed-off-by: Jens Langhammer <jens.langhammer@beryju.org> * start custom tag, more rebrand Signed-off-by: Jens Langhammer <jens.langhammer@beryju.org> * add default flows Signed-off-by: Jens Langhammer <jens.langhammer@beryju.org> * move blueprints out of website Signed-off-by: Jens Langhammer <jens.langhammer@beryju.org> * try new things Signed-off-by: Jens Langhammer <jens.langhammer@beryju.org> * add !lookup, fix web Signed-off-by: Jens Langhammer <jens.langhammer@beryju.org> * update and cleanup default Signed-off-by: Jens Langhammer <jens.langhammer@beryju.org> * fix tags in lists Signed-off-by: Jens Langhammer <jens.langhammer@beryju.org> * don't save field if its set to default value Signed-off-by: Jens Langhammer <jens.langhammer@beryju.org> * more flow cleanup Signed-off-by: Jens Langhammer <jens.langhammer@beryju.org> * format web Signed-off-by: Jens Langhammer <jens.langhammer@beryju.org> * fix missing serializer for sms Signed-off-by: Jens Langhammer <jens.langhammer@beryju.org> * ignore _set fields Signed-off-by: Jens Langhammer <jens.langhammer@beryju.org> * remove custom file extension Signed-off-by: Jens Langhammer <jens.langhammer@beryju.org> * migrate default flow to tenant Signed-off-by: Jens Langhammer <jens.langhammer@beryju.org> * include blueprints Signed-off-by: Jens Langhammer <jens.langhammer@beryju.org> * fix tests Signed-off-by: Jens Langhammer <jens.langhammer@beryju.org>
56 lines
2 KiB
Markdown
56 lines
2 KiB
Markdown
---
|
|
title: Example Flows
|
|
---
|
|
|
|
:::info
|
|
You can apply these flows multiple times to stay updated, however this will discard all changes you've made.
|
|
:::
|
|
|
|
:::info
|
|
The example flows provided below will **override** the default flows, please review the contents of the example flow before importing and consider exporting the affected existing flows first.
|
|
:::
|
|
|
|
## Enrollment (2 Stage)
|
|
|
|
Flow: right-click [here](/blueprints/example/flows-enrollment-2-stage.yaml) and save the file.
|
|
|
|
Sign-up flow for new users, which prompts them for their username, email, password and name. No verification is done. Users are also immediately logged on after this flow.
|
|
|
|
## Enrollment with email verification
|
|
|
|
Flow: right-click [here](/blueprints/example/flows-enrollment-email-verification.yaml) and save the file.
|
|
|
|
Same flow as above, with an extra email verification stage.
|
|
|
|
You'll probably have to adjust the Email stage and set your connection details.
|
|
|
|
## Two-factor Login
|
|
|
|
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 with conditional Captcha
|
|
|
|
Flow: right-click [here](/blueprints/example/flows-login-conditional-captcha.yaml) and save the file.
|
|
|
|
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)
|
|
|
|
## Recovery with email verification
|
|
|
|
Flow: right-click [here](/blueprints/example/flows-recovery-email-verification.yaml) and save the file.
|
|
|
|
Recovery flow, the user is sent an email after they've identified themselves. After they click on the link in the email, they are prompted for a new password and immediately logged on.
|
|
|
|
## User deletion
|
|
|
|
Flow: right-click [here](/blueprints/example/flows-unenrollment.yaml) and save the file.
|
|
|
|
Flow for users to delete their account,
|
|
|
|
:::warning
|
|
This is done without any warning.
|
|
:::
|