blob: 0ef12dc775ec39fcfe927ed6ffa856f99db7e2b7 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
|
# Admin Documentation
## Gateways
Here you can find the configuration instructors for the currently supported gateways.
### playSMS
Url: https://playsms.org/
Stability: Experimental
Use the Webservices provided by playSMS for sending SMS.
Interactive admin configuration:
```bash
occ twofactorauth:gateway:configure sms
```
### Signal
Url: https://www.signal.org/
Stability: Experimental
This gateways allows you to send messages via the Signal protocol. The Signal gateway can be
run as Docker container. The image for gateway including setup instructions can be found on
[GitLab](https://gitlab.com/morph027/signal-web-gateway).
*Note: Signal users are bound to phone numbers. If you already use Signal on your phone, you need a separate number for the gateway's registration.*
Once you've set up the gateway, you can configure this app interactively:
```bash
occ twofactorauth:gateway:configure signal
```
### Telegram
Url: https://www.telegram.org/
Stability: Unstable
In order to send messages via the Telegram network, you have to register a [Telegram Bot](https://core.telegram.org/bots). This bot is used to send authentication codes to users after they have initiated a conversation and entered their Telegram ID.
Once you've got your bot's token, follow the interactive configuration command:
```bash
occ twofactorauth:gateway:configure telegram
```
### websms.de
Url: https://websms.de/
Stability: Stable
Interactive admin configuration:
```bash
occ twofactorauth:gateway:configure sms
```
|
