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

docs: fix minor grammar issues

This commit is contained in:
Jens Langhammer 2021-01-13 10:28:02 +01:00
parent c180c4b1a2
commit 9c5bb3998c
2 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
website/docs/events/notifications.md
View File

@ -6,13 +6,13 @@ title: Notifications
Starting with authentik 0.15, you can create notification triggers, which can alert you based on the creation of certain events. Starting with authentik 0.15, you can create notification triggers, which can alert you based on the creation of certain events.
Filtering is done by using the Policy Engine. You can do simple filtering using the "Event Matcher Policy" type Filtering is done by using the Policy Engine. You can do simple filtering using the "Event Matcher Policy" type.
![](./event_matcher.png) ![](./event_matcher.png)
An Event has to match all configured fields, otherwise it will not match. An event has to match all configured fields, otherwise the trigger will not activate.
To match events with an "Expression Policy", you can write code like so To match events with an "Expression Policy", you can write code like so:
```python ```python
if "event" not in request.context: if "event" not in request.context:
@ -23,9 +23,9 @@ return ip_address(request.context["evnet"].client_ip) in ip_network('192.0.2.0/2
## Selecting who gets notified ## Selecting who gets notified
After you've create the policies to match the events you want, create a "Notification Trigger". After you've created the policies to match the events you want, create a "Notification Trigger".
You have to select which group the generated notification should be sent to. If left empty, the trigger will be disabled. You have to select which group the generated notification should be sent to. If left empty, the trigger will be disabled.
You also have to select which transports should be used to send the Notification. You also have to select which transports should be used to send the notification.
A transport with the name "default-email-transport" is created by default. This transport will use the [global email configuration](../installation/docker-compose#email-configuration-optional-but-recommended) A transport with the name "default-email-transport" is created by default. This transport will use the [global email configuration](../installation/docker-compose#email-configuration-optional-but-recommended).

6
website/docs/events/transports.md
View File

@ -2,7 +2,7 @@
title: Transports title: Transports
--- ---
Notifications can be sent to users via multiple mediums. Per default, the [global email configuration](../installation/docker-compose#email-configuration-optional-but-recommended) will be used. Notifications can be sent to users via multiple mediums. By default, the [global email configuration](../installation/docker-compose#email-configuration-optional-but-recommended) will be used.
## Generic Webhook ## Generic Webhook
@ -17,7 +17,7 @@ This will send a POST request to the given URL with the following contents:
} }
``` ```
The `Content-Type` Header is set to `text/json`. The `Content-Type` header is set to `text/json`.
:::warning :::warning
This will send a request for each user of the group selected in the trigger. This will send a request for each user of the group selected in the trigger.
@ -25,4 +25,4 @@ This will send a request for each user of the group selected in the trigger.
## Slack Webhook ## Slack Webhook
This sends a request using the Slack-specific format. This is also compatible with Discord's Webhooks by appending `/slack`. This sends a request using the Slack-specific format. This is also compatible with Discord's webhooks by appending `/slack` to the Discord webhook URL.