From cf6be9562bf5a727d3885747890833738b5f3336 Mon Sep 17 00:00:00 2001 From: Suguru Hirahara Date: Mon, 23 Dec 2024 14:23:51 +0900 Subject: [PATCH] Update docs/configuring-playbook-user-verification-service.md: use abbreviation See the line 3. Signed-off-by: Suguru Hirahara --- docs/configuring-playbook-user-verification-service.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/configuring-playbook-user-verification-service.md b/docs/configuring-playbook-user-verification-service.md index b74b4fbd8..63c5d4bf5 100644 --- a/docs/configuring-playbook-user-verification-service.md +++ b/docs/configuring-playbook-user-verification-service.md @@ -6,7 +6,7 @@ See the project's [documentation](https://github.com/matrix-org/matrix-user-veri Currently, the main purpose of this role is to allow Jitsi to authenticate Matrix users and check if they are authorized to join a conference. -**Note**: enabling Matrix User Verification Service, means that the `openid` API endpoints will be exposed on the Matrix Federation port (usually `8448`), even if [federation](configuring-playbook-federation.md) is disabled. +**Note**: enabling UVS, means that the `openid` API endpoints will be exposed on the Matrix Federation port (usually `8448`), even if [federation](configuring-playbook-federation.md) is disabled. If the Jitsi server is also configured by this playbook, all plugging of variables and secrets is handled in `group_vars/matrix_servers`. @@ -43,7 +43,7 @@ ansible-playbook -i inventory/hosts setup.yml --extra-vars='username=uvs passwor ## Adjusting the playbook configuration -To enable Matrix User Verification Service, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: +To enable UVS, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file: ```yaml matrix_user_verification_service_enabled: true