docs(exampleFlows): Rename pbflow to akflow (#596)
* docs(exampleFlows): Rename enrollment-2-stage.pbflow * docs(exampleFlows): Rename enrollment-email-verification.pbflow * docs(exampleFlows): Rename login-2fa.pbflow * docs(exampleFlows): Rename login-conditional-captcha.pbflow * docs(exampleFlows): Rename recovery-email-verification.pbflow * docs(exampleFlows): Rename unenrollment.pbflow * docs(exampleFlows): Fix links.
This commit is contained in:
tigattack
GitHub
parent
e3f7bd8ab8
commit
085589bcec
|
|
@ -8,13 +8,13 @@ You can apply theses flows multiple times to stay updated, however this will dis
|
||||||
|
|
||||||
## Enrollment (2 Stage)
|
## Enrollment (2 Stage)
|
||||||
|
|
||||||
Flow: right-click [here](/flows/enrollment-2-stage.pbflow) and save the file.
|
Flow: right-click [here](/flows/enrollment-2-stage.akflow) 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.
|
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
|
## Enrollment with email verification
|
||||||
|
|
||||||
Flow: right-click [here](/flows/enrollment-email-verification.pbflow) and save the file.
|
Flow: right-click [here](/flows/enrollment-email-verification.akflow) and save the file.
|
||||||
|
|
||||||
Same flow as above, with an extra email verification stage.
|
Same flow as above, with an extra email verification stage.
|
||||||
|
|
||||||
|
|
@ -22,13 +22,13 @@ You'll probably have to adjust the Email stage and set your connection details.
|
||||||
|
|
||||||
## Two-factor Login
|
## Two-factor Login
|
||||||
|
|
||||||
Flow: right-click [here](/flows/login-2fa.pbflow) and save the file.
|
Flow: right-click [here](/flows/login-2fa.akflow) 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
|
||||||
|
|
||||||
## Login with conditional Captcha
|
## Login with conditional Captcha
|
||||||
|
|
||||||
Flow: right-click [here](/flows/login-conditional-captcha.pbflow) and save the file.
|
Flow: right-click [here](/flows/login-conditional-captcha.akflow) and save the file.
|
||||||
|
|
||||||
Login flow which conditionally shows the users a captcha, based on the reputation of their IP and Username.
|
Login flow which conditionally shows the users a captcha, based on the reputation of their IP and Username.
|
||||||
|
|
||||||
|
|
@ -36,13 +36,13 @@ By default, the captcha test keys are used. You can get a proper key [here](http
|
||||||
|
|
||||||
## Recovery with email verification
|
## Recovery with email verification
|
||||||
|
|
||||||
Flow: right-click [here](/flows/recovery-email-verification.pbflow) and save the file.
|
Flow: right-click [here](/flows/recovery-email-verification.akflow) 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.
|
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
|
## User deletion
|
||||||
|
|
||||||
Flow: right-click [here](/flows/unenrollment.pbflow) and save the file.
|
Flow: right-click [here](/flows/unenrollment.akflow) and save the file.
|
||||||
|
|
||||||
Flow for users to delete their account,
|
Flow for users to delete their account,
|
||||||
|
|
||||||
|
|
|
||||||
Reference in New Issue