finallycoffee/matrix-docker-ansible-deploy
5
1
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Update beeper-linkedin configuration to latest upstream config and properly pass double-puppeting login shared secrets

Browse Source 
We used to pass the shared secret for double-puppeting via a
`login_shared_secret` parameter, which doesn't seem to exist anymore.
The proper way to do it is via `login_shared_secret_map`.

The comments for `login_shared_secret_map` seem to indicate that it's
only usable with the shared-secret-auth password provider.

However, this bridge is based on mautrix-python (`>=0.20.5,<0.21`) as
per its `requirements.txt`
Support for double-puppeting via arbitrary access tokens landed in
mautrix-python 0.20.1 (6f25b62e80/CHANGELOG.md (L44-L53)),
so it should be possible to use appservice double-puppet.
Related to af04ca1238

A bunch of other parameters seem to have moved around as well.

This patch introduces some new Ansible variables for controlling
additional settings related to encryption, etc.
This commit is contained in:
Slavi Pantaleev
2024-12-02 20:00:08 +02:00
parent e5a2935d0f
commit 2c719b2ef7
6 changed files with 202 additions and 99 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
docs/configuring-playbook-bridge-beeper-linkedin.md
View File

@ -17,11 +17,8 @@ There are some additional things you may wish to configure about the bridge befo
Encryption support is off by default. If you would like to enable encryption, add the following to your `vars.yml` file:
```yaml
matrix_beeper_linkedin_configuration_extension_yaml: |
bridge:
encryption:
allow: true
default: true
matrix_beeper_linkedin_bridge_encryption_allow: true
matrix_beeper_linkedin_bridge_encryption_default: true
```
If you would like to be able to administrate the bridge from your account it can be configured like this: