habsi/authentik
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

website/docs: 2024.2 release notes (#8468)

Browse Source 
Co-authored-by: Tana M Berry <tanamarieberry@yahoo.com>
Co-authored-by: Jens L. <jens@goauthentik.io>
Co-authored-by: Jens Langhammer <jens@goauthentik.io>
This commit is contained in:
Marc 'risson' Schmitt
2024-02-14 20:52:56 +01:00
committed by GitHub
parent 2c1df6702c
commit a3bfb3d25c
13 changed files with 10235 additions and 129 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
website/docs/flow/stages/email/index.mdx
View File

@ -26,7 +26,7 @@ return True
You can also use custom email templates, to use your own design or layout.
:::info
Starting with authentik 2024.1, it is possible to create `.txt` files with the same name as the `.html` template. If a matching `.txt` file exists, the email sent will be a multipart email with both the text and HTML template.
Starting with authentik 2024.2, it is possible to create `.txt` files with the same name as the `.html` template. If a matching `.txt` file exists, the email sent will be a multipart email with both the text and HTML template.
:::
import Tabs from "@theme/Tabs";

2
website/docs/flow/stages/identification/index.md
View File

@ -25,7 +25,7 @@ These fields specify if and which flows are linked on the form. The enrollment f
## Pretend user exists
:::info
Requires authentik 2024.1
Requires authentik 2024.2
:::
When enabled, any user identifier will be accepted as valid (as long as they match the correct format, i.e. when [User fields](#user-fields) is set to only allow Emails, then the identifier still needs to be an Email). The stage will succeed and the flow will continue to the next stage. Stages like the [Password stage](../password/index.md) and [Email stage](../email/index.mdx) are aware of this "pretend" user and will behave the same as if the user would exist.

4
website/docs/flow/stages/user_login/index.md
View File

@ -39,8 +39,6 @@ When configured, all sessions authenticated by this stage will be bound to the s
Sessions which break this binding will be terminated on use. The created [`logout`](../../../events/index.md#logout) event will contain additional data related to what caused the binding to be broken:
```json
Context
{
"asn": {
"asn": 6805,
@ -65,7 +63,7 @@ Context
},
"ip": {
"previous": "1.2.3.4",
"new": "5.6.7.8",
"new": "5.6.7.8"
},
"http_request": {
"args": {},