overmind
/
matrix-docker-ansible-deploy
şunun yansıması https://github.com/spantaleev/matrix-docker-ansible-deploy
1
0
Çatalla 0
Kod Konular 0 Sürümler 0 Wiki Aktivite
Matrix Docker Ansible eploy
25'ten fazla konu seçemezsiniz Konular bir harf veya rakamla başlamalı, kısa çizgiler ('-') içerebilir ve en fazla 35 karakter uzunluğunda olabilir.
9961 İşleme
13 Dallar
10 GiB
 
 
Dal: element-call-stack
Dallar Biçim İmleri
${ item.name }
${ searchTerm } dalı oluştur
'element-call-stack'den
${ noResults }
matrix-docker-ansible-deploy/i18n/locales/bg/LC_MESSAGES/docs/configuring-playbook-user-v...

235 satır
12 KiB
Ham Kalıcı Bağlantı Suçlama Geçmiş 

  1. # SOME DESCRIPTIVE TITLE.

  2. # Copyright (C) 2018-2024, Slavi Pantaleev, Aine Etke, MDAD community

  3. # members

  4. # This file is distributed under the same license as the

  5. # matrix-docker-ansible-deploy package.

  6. # FIRST AUTHOR <EMAIL@ADDRESS>, 2024.

  7. #

  8. #, fuzzy

  9. msgid ""

  10. msgstr ""

  11. "Project-Id-Version: matrix-docker-ansible-deploy \n"

  12. "Report-Msgid-Bugs-To: \n"

  13. "POT-Creation-Date: 2025-01-27 09:54+0200\n"

  14. "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"

  15. "Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"

  16. "Language: bg\n"

  17. "Language-Team: bg <LL@li.org>\n"

  18. "Plural-Forms: nplurals=2; plural=(n != 1);\n"

  19. "MIME-Version: 1.0\n"

  20. "Content-Type: text/plain; charset=utf-8\n"

  21. "Content-Transfer-Encoding: 8bit\n"

  22. "Generated-By: Babel 2.16.0\n"

  23. 

  24. #: ../../../docs/configuring-playbook-user-verification-service.md:1

  25. msgid "Setting up Matrix User Verification Service (optional)"

  26. msgstr ""

  27. 

  28. #: ../../../docs/configuring-playbook-user-verification-service.md:3

  29. msgid "The playbook can install and configure [Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service) (hereafter: UVS) for you."

  30. msgstr ""

  31. 

  32. #: ../../../docs/configuring-playbook-user-verification-service.md:5

  33. msgid "See the project's [documentation](https://github.com/matrix-org/matrix-user-verification-service/blob/master/README.md) to learn what it does and why it might be useful to you."

  34. msgstr ""

  35. 

  36. #: ../../../docs/configuring-playbook-user-verification-service.md:7

  37. msgid "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. If the Jitsi server is also configured by this playbook, all plugging of variables and secrets is handled in `group_vars/matrix_servers`."

  38. msgstr ""

  39. 

  40. #: ../../../docs/configuring-playbook-user-verification-service.md:9

  41. msgid "What does it do?"

  42. msgstr ""

  43. 

  44. #: ../../../docs/configuring-playbook-user-verification-service.md:11

  45. msgid "UVS can be used to verify two claims:"

  46. msgstr ""

  47. 

  48. #: ../../../docs/configuring-playbook-user-verification-service.md:13

  49. msgid "(A) Whether a given OpenID token is valid for a given server and"

  50. msgstr ""

  51. 

  52. #: ../../../docs/configuring-playbook-user-verification-service.md:14

  53. msgid "(B) whether a user is member of a given room and the corresponding PowerLevel"

  54. msgstr ""

  55. 

  56. #: ../../../docs/configuring-playbook-user-verification-service.md:16

  57. msgid "Verifying an OpenID token ID done by finding the corresponding Homeserver via `/.well-known/matrix/server` for the given domain. The configured `matrix_user_verification_service_uvs_homeserver_url` does **not** factor into this. By default, this playbook only checks against `matrix_server_fqn_matrix`. Therefore, the request will be made against the public `openid` API for `matrix_server_fqn_matrix`."

  58. msgstr ""

  59. 

  60. #: ../../../docs/configuring-playbook-user-verification-service.md:18

  61. msgid "Verifying RoomMembership and PowerLevel is done against `matrix_user_verification_service_uvs_homeserver_url` which is by default done via the docker network. UVS will verify the validity of the token beforehand though."

  62. msgstr ""

  63. 

  64. #: ../../../docs/configuring-playbook-user-verification-service.md:20

  65. msgid "Prerequisites"

  66. msgstr ""

  67. 

  68. #: ../../../docs/configuring-playbook-user-verification-service.md:22

  69. msgid "Open Matrix Federation port"

  70. msgstr ""

  71. 

  72. #: ../../../docs/configuring-playbook-user-verification-service.md:24

  73. msgid "Enabling the UVS service will automatically reconfigure your Synapse homeserver to expose the `openid` API endpoints on the Matrix Federation port (usually `8448`), even if [federation](configuring-playbook-federation.md) is disabled. If you enable the component, make sure that the port is accessible."

  74. msgstr ""

  75. 

  76. #: ../../../docs/configuring-playbook-user-verification-service.md:26

  77. msgid "Install Matrix services"

  78. msgstr ""

  79. 

  80. #: ../../../docs/configuring-playbook-user-verification-service.md:28

  81. msgid "UVS can only be installed after Matrix services are installed and running. If you're just installing Matrix services for the first time, please continue with the [Configuration](configuring-playbook.md) / [Installation](installing.md) and come back here later."

  82. msgstr ""

  83. 

  84. #: ../../../docs/configuring-playbook-user-verification-service.md:30

  85. msgid "Register a dedicated Matrix user (optional, recommended)"

  86. msgstr ""

  87. 

  88. #: ../../../docs/configuring-playbook-user-verification-service.md:32

  89. msgid "We recommend that you create a dedicated Matrix user for uvs (`uvs` is a good username). **Because UVS requires an access token as an admin user, that user needs to be an admin.**"

  90. msgstr ""

  91. 

  92. #: ../../../docs/configuring-playbook-user-verification-service.md:34

  93. msgid "Generate a strong password for the user. You can create one with a command like `pwgen -s 64 1`."

  94. msgstr ""

  95. 

  96. #: ../../../docs/configuring-playbook-user-verification-service.md:36

  97. msgid "You can use the playbook to [register a new user](registering-users.md):"

  98. msgstr ""

  99. 

  100. #: ../../../docs/configuring-playbook-user-verification-service.md:42

  101. msgid "Obtain an access token"

  102. msgstr ""

  103. 

  104. #: ../../../docs/configuring-playbook-user-verification-service.md:44

  105. msgid "UVS requires an access token as an admin user to verify RoomMembership and PowerLevel against `matrix_user_verification_service_uvs_homeserver_url`. Refer to the documentation on [how to obtain an access token](obtaining-access-tokens.md)."

  106. msgstr ""

  107. 

  108. #: ../../../docs/configuring-playbook-user-verification-service.md:46

  109. msgid "[!WARNING] Access tokens are sensitive information. Do not include them in any bug reports, messages, or logs. Do not share the access token with anyone."

  110. msgstr ""

  111. 

  112. #: ../../../docs/configuring-playbook-user-verification-service.md:49

  113. msgid "Adjusting the playbook configuration"

  114. msgstr ""

  115. 

  116. #: ../../../docs/configuring-playbook-user-verification-service.md:51

  117. msgid "To enable UVS, add the following configuration to your `inventory/host_vars/matrix.example.com/vars.yml` file. Make sure to replace `ACCESS_TOKEN_HERE` with the one created [above](#obtain-an-access-token)."

  118. msgstr ""

  119. 

  120. #: ../../../docs/configuring-playbook-user-verification-service.md:59

  121. msgid "In the default configuration, the UVS Server is only reachable via the docker network, which is fine if e.g. Jitsi is also running in a container on the host. However, it is possible to expose UVS via setting `matrix_user_verification_service_container_http_host_bind_port`."

  122. msgstr ""

  123. 

  124. #: ../../../docs/configuring-playbook-user-verification-service.md:61

  125. msgid "Custom Auth Token (optional)"

  126. msgstr ""

  127. 

  128. #: ../../../docs/configuring-playbook-user-verification-service.md:63

  129. msgid "It is possible to set an API Auth Token to restrict access to the UVS. If this is enabled, anyone making a request to UVS must provide it via the header `Authorization: Bearer YOUR_TOKEN_HERE`."

  130. msgstr ""

  131. 

  132. #: ../../../docs/configuring-playbook-user-verification-service.md:65

  133. msgid "By default, the token (`YOUR_TOKEN_HERE`) will be derived from `matrix_homeserver_generic_secret_key` in `group_vars/matrix_servers`."

  134. msgstr ""

  135. 

  136. #: ../../../docs/configuring-playbook-user-verification-service.md:67

  137. msgid "To set your own token, add the following configuration to your `vars.yml` file. Make sure to replace `YOUR_TOKEN_HERE` with your own."

  138. msgstr ""

  139. 

  140. #: ../../../docs/configuring-playbook-user-verification-service.md:73

  141. msgid "If a Jitsi instance is also managed by this playbook and [`matrix` authentication](configuring-playbook-jitsi.md#authenticate-using-matrix-openid-auth-type-matrix) is enabled there, this collection will automatically configure Jitsi to use the configured auth token."

  142. msgstr ""

  143. 

  144. #: ../../../docs/configuring-playbook-user-verification-service.md:75

  145. msgid "Disable Authorization (optional)"

  146. msgstr ""

  147. 

  148. #: ../../../docs/configuring-playbook-user-verification-service.md:77

  149. msgid "Authorization is enabled by default. To disable it, add the following configuration to your `vars.yml` file:"

  150. msgstr ""

  151. 

  152. #: ../../../docs/configuring-playbook-user-verification-service.md:83

  153. msgid "Federation (optional)"

  154. msgstr ""

  155. 

  156. #: ../../../docs/configuring-playbook-user-verification-service.md:85

  157. msgid "In theory (however currently untested), UVS can handle federation. To enable it, add the following configuration to your `vars.yml` file:"

  158. msgstr ""

  159. 

  160. #: ../../../docs/configuring-playbook-user-verification-service.md:91

  161. msgid "This will instruct UVS to verify the OpenID token against any domain given in a request. Homeserver discovery is done via `.well-known/matrix/server` of the given domain."

  162. msgstr ""

  163. 

  164. #: ../../../docs/configuring-playbook-user-verification-service.md:93

  165. msgid "Extending the configuration"

  166. msgstr ""

  167. 

  168. #: ../../../docs/configuring-playbook-user-verification-service.md:95

  169. msgid "There are some additional things you may wish to configure about the component."

  170. msgstr ""

  171. 

  172. #: ../../../docs/configuring-playbook-user-verification-service.md:97

  173. msgid "Take a look at:"

  174. msgstr ""

  175. 

  176. #: ../../../docs/configuring-playbook-user-verification-service.md:99

  177. msgid "`roles/custom/matrix-user-verification-service/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"

  178. msgstr ""

  179. 

  180. #: ../../../docs/configuring-playbook-user-verification-service.md:101

  181. msgid "Installing"

  182. msgstr ""

  183. 

  184. #: ../../../docs/configuring-playbook-user-verification-service.md:103

  185. msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"

  186. msgstr ""

  187. 

  188. #: ../../../docs/configuring-playbook-user-verification-service.md:110

  189. msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-service matrix-user-verification-service` or `just setup-all`"

  190. msgstr ""

  191. 

  192. #: ../../../docs/configuring-playbook-user-verification-service.md:112

  193. msgid "`just install-service matrix-user-verification-service` is useful for maintaining your setup quickly when its components remain unchanged. If you adjust your `vars.yml` to remove other components, you'd need to run `just setup-all`, or these components will still remain installed. Note `just setup-all` runs the `ensure-matrix-users-created` tag too."

  194. msgstr ""

  195. 

  196. #: ../../../docs/configuring-playbook-user-verification-service.md:114

  197. msgid "Troubleshooting"

  198. msgstr ""

  199. 

  200. #: ../../../docs/configuring-playbook-user-verification-service.md:116

  201. msgid "As with all other services, you can find the logs in [systemd-journald](https://www.freedesktop.org/software/systemd/man/systemd-journald.service.html) by logging in to the server with SSH and running `journalctl -fu matrix-user-verification-service`."

  202. msgstr ""

  203. 

  204. #: ../../../docs/configuring-playbook-user-verification-service.md:118

  205. msgid "Increase logging verbosity"

  206. msgstr ""

  207. 

  208. #: ../../../docs/configuring-playbook-user-verification-service.md:120

  209. msgid "The default logging level for this component is `info`. If you want to increase the verbosity, add the following configuration to your `vars.yml` file and re-run the playbook:"

  210. msgstr ""

  211. 

  212. #: ../../../docs/configuring-playbook-user-verification-service.md:127

  213. msgid "TLS Certificate Checking"

  214. msgstr ""

  215. 

  216. #: ../../../docs/configuring-playbook-user-verification-service.md:129

  217. msgid "If the Matrix Homeserver does not provide a valid TLS certificate, UVS will fail with the following error message:"

  218. msgstr ""

  219. 

  220. #: ../../../docs/configuring-playbook-user-verification-service.md:131

  221. msgid "message: 'No response received: [object Object]',"

  222. msgstr ""

  223. 

  224. #: ../../../docs/configuring-playbook-user-verification-service.md:133

  225. msgid "This also applies to self-signed and Let's Encrypt staging certificates."

  226. msgstr ""

  227. 

  228. #: ../../../docs/configuring-playbook-user-verification-service.md:135

  229. msgid "To disable certificate validation altogether (INSECURE! Not suitable for production use!) set: `NODE_TLS_REJECT_UNAUTHORIZED=0`"

  230. msgstr ""

  231. 

  232. #: ../../../docs/configuring-playbook-user-verification-service.md:137

  233. msgid "Alternatively, it is possible to inject your own CA certificates into the container by mounting a PEM file with additional trusted CAs into the container and pointing the `NODE_EXTRA_CA_CERTS` environment variable to it."

  234. msgstr ""