fixed bridge permissions

This commit is contained in:
Sabine Laszakovits 2020-10-25 21:42:40 +01:00
parent 2211e678f3
commit dd50ee19ab
3 changed files with 24 additions and 3 deletions

View file

@ -10,6 +10,20 @@ Use the following playbook configuration:
matrix_mautrix_signal_enabled: true
```
To specify which users have access to the bridge, use the variable `matrix_mautrix_signal_configuration_permissions`.
Refer to the documentation for
```yaml
bridge:
permissions:
```
in [the example config in mautrix-signal](https://github.com/tulir/mautrix-signal/blob/master/mautrix_signal/example-config.yaml).
For instance, use
```yaml
matrix_mautrix_signal_configuration_permissions:
"YOUR_DOMAIN": user
```
to allow all users registered to `YOUR_DOMAIN` access to the bridge (where `YOUR_DOMAIN` is your base domain, not the `matrix.` domain).
## Set up Double Puppeting

View file

@ -62,6 +62,15 @@ matrix_mautrix_signal_login_shared_secret: ''
# or completely replace this variable with your own template.
matrix_mautrix_signal_configuration_yaml: "{{ lookup('template', 'templates/config.yaml.j2') }}"
# Permitted values:
# user - Use the bridge with puppeting.
# admin - Use and administrate the bridge.
# Permitted keys:
# * - All Matrix users
# domain - All users on that homeserver
# mxid - Specific user
matrix_mautrix_signal_configuration_permissions: []
matrix_mautrix_signal_configuration_extension_yaml: |
# Your custom YAML configuration goes here.
# This configuration extends the default starting configuration (`matrix_mautrix_signal_configuration_yaml`).

View file

@ -170,9 +170,7 @@ bridge:
# * - All Matrix users
# domain - All users on that homeserver
# mxid - Specific user
permissions:
"1m.at": "user"
"@admin:1m.at": "admin"
permissions: {{ matrix_mautrix_signal_configuration_permissions }}
# Python logging configuration.