Matrix Docker Ansible eploy
25개 이상의 토픽을 선택하실 수 없습니다. Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 

234 lines
12 KiB

  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: jp\n"
  17. "Language-Team: jp <LL@li.org>\n"
  18. "MIME-Version: 1.0\n"
  19. "Content-Type: text/plain; charset=utf-8\n"
  20. "Content-Transfer-Encoding: 8bit\n"
  21. "Generated-By: Babel 2.16.0\n"
  22. #: ../../../docs/configuring-playbook-user-verification-service.md:1
  23. msgid "Setting up Matrix User Verification Service (optional)"
  24. msgstr ""
  25. #: ../../../docs/configuring-playbook-user-verification-service.md:3
  26. msgid "The playbook can install and configure [Matrix User Verification Service](https://github.com/matrix-org/matrix-user-verification-service) (hereafter: UVS) for you."
  27. msgstr ""
  28. #: ../../../docs/configuring-playbook-user-verification-service.md:5
  29. 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."
  30. msgstr ""
  31. #: ../../../docs/configuring-playbook-user-verification-service.md:7
  32. 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`."
  33. msgstr ""
  34. #: ../../../docs/configuring-playbook-user-verification-service.md:9
  35. msgid "What does it do?"
  36. msgstr ""
  37. #: ../../../docs/configuring-playbook-user-verification-service.md:11
  38. msgid "UVS can be used to verify two claims:"
  39. msgstr ""
  40. #: ../../../docs/configuring-playbook-user-verification-service.md:13
  41. msgid "(A) Whether a given OpenID token is valid for a given server and"
  42. msgstr ""
  43. #: ../../../docs/configuring-playbook-user-verification-service.md:14
  44. msgid "(B) whether a user is member of a given room and the corresponding PowerLevel"
  45. msgstr ""
  46. #: ../../../docs/configuring-playbook-user-verification-service.md:16
  47. 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`."
  48. msgstr ""
  49. #: ../../../docs/configuring-playbook-user-verification-service.md:18
  50. 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."
  51. msgstr ""
  52. #: ../../../docs/configuring-playbook-user-verification-service.md:20
  53. msgid "Prerequisites"
  54. msgstr ""
  55. #: ../../../docs/configuring-playbook-user-verification-service.md:22
  56. msgid "Open Matrix Federation port"
  57. msgstr ""
  58. #: ../../../docs/configuring-playbook-user-verification-service.md:24
  59. 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."
  60. msgstr ""
  61. #: ../../../docs/configuring-playbook-user-verification-service.md:26
  62. msgid "Install Matrix services"
  63. msgstr ""
  64. #: ../../../docs/configuring-playbook-user-verification-service.md:28
  65. 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."
  66. msgstr ""
  67. #: ../../../docs/configuring-playbook-user-verification-service.md:30
  68. msgid "Register a dedicated Matrix user (optional, recommended)"
  69. msgstr ""
  70. #: ../../../docs/configuring-playbook-user-verification-service.md:32
  71. 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.**"
  72. msgstr ""
  73. #: ../../../docs/configuring-playbook-user-verification-service.md:34
  74. msgid "Generate a strong password for the user. You can create one with a command like `pwgen -s 64 1`."
  75. msgstr ""
  76. #: ../../../docs/configuring-playbook-user-verification-service.md:36
  77. msgid "You can use the playbook to [register a new user](registering-users.md):"
  78. msgstr ""
  79. #: ../../../docs/configuring-playbook-user-verification-service.md:42
  80. msgid "Obtain an access token"
  81. msgstr ""
  82. #: ../../../docs/configuring-playbook-user-verification-service.md:44
  83. 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)."
  84. msgstr ""
  85. #: ../../../docs/configuring-playbook-user-verification-service.md:46
  86. 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."
  87. msgstr ""
  88. #: ../../../docs/configuring-playbook-user-verification-service.md:49
  89. msgid "Adjusting the playbook configuration"
  90. msgstr ""
  91. #: ../../../docs/configuring-playbook-user-verification-service.md:51
  92. 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)."
  93. msgstr ""
  94. #: ../../../docs/configuring-playbook-user-verification-service.md:59
  95. 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`."
  96. msgstr ""
  97. #: ../../../docs/configuring-playbook-user-verification-service.md:61
  98. msgid "Custom Auth Token (optional)"
  99. msgstr ""
  100. #: ../../../docs/configuring-playbook-user-verification-service.md:63
  101. 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`."
  102. msgstr ""
  103. #: ../../../docs/configuring-playbook-user-verification-service.md:65
  104. msgid "By default, the token (`YOUR_TOKEN_HERE`) will be derived from `matrix_homeserver_generic_secret_key` in `group_vars/matrix_servers`."
  105. msgstr ""
  106. #: ../../../docs/configuring-playbook-user-verification-service.md:67
  107. 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."
  108. msgstr ""
  109. #: ../../../docs/configuring-playbook-user-verification-service.md:73
  110. 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."
  111. msgstr ""
  112. #: ../../../docs/configuring-playbook-user-verification-service.md:75
  113. msgid "Disable Authorization (optional)"
  114. msgstr ""
  115. #: ../../../docs/configuring-playbook-user-verification-service.md:77
  116. msgid "Authorization is enabled by default. To disable it, add the following configuration to your `vars.yml` file:"
  117. msgstr ""
  118. #: ../../../docs/configuring-playbook-user-verification-service.md:83
  119. msgid "Federation (optional)"
  120. msgstr ""
  121. #: ../../../docs/configuring-playbook-user-verification-service.md:85
  122. msgid "In theory (however currently untested), UVS can handle federation. To enable it, add the following configuration to your `vars.yml` file:"
  123. msgstr ""
  124. #: ../../../docs/configuring-playbook-user-verification-service.md:91
  125. 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."
  126. msgstr ""
  127. #: ../../../docs/configuring-playbook-user-verification-service.md:93
  128. msgid "Extending the configuration"
  129. msgstr ""
  130. #: ../../../docs/configuring-playbook-user-verification-service.md:95
  131. msgid "There are some additional things you may wish to configure about the component."
  132. msgstr ""
  133. #: ../../../docs/configuring-playbook-user-verification-service.md:97
  134. msgid "Take a look at:"
  135. msgstr ""
  136. #: ../../../docs/configuring-playbook-user-verification-service.md:99
  137. msgid "`roles/custom/matrix-user-verification-service/defaults/main.yml` for some variables that you can customize via your `vars.yml` file"
  138. msgstr ""
  139. #: ../../../docs/configuring-playbook-user-verification-service.md:101
  140. msgid "Installing"
  141. msgstr ""
  142. #: ../../../docs/configuring-playbook-user-verification-service.md:103
  143. msgid "After configuring the playbook, run it with [playbook tags](playbook-tags.md) as below:"
  144. msgstr ""
  145. #: ../../../docs/configuring-playbook-user-verification-service.md:110
  146. msgid "The shortcut commands with the [`just` program](just.md) are also available: `just install-service matrix-user-verification-service` or `just setup-all`"
  147. msgstr ""
  148. #: ../../../docs/configuring-playbook-user-verification-service.md:112
  149. 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."
  150. msgstr ""
  151. #: ../../../docs/configuring-playbook-user-verification-service.md:114
  152. msgid "Troubleshooting"
  153. msgstr ""
  154. #: ../../../docs/configuring-playbook-user-verification-service.md:116
  155. 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`."
  156. msgstr ""
  157. #: ../../../docs/configuring-playbook-user-verification-service.md:118
  158. msgid "Increase logging verbosity"
  159. msgstr ""
  160. #: ../../../docs/configuring-playbook-user-verification-service.md:120
  161. 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:"
  162. msgstr ""
  163. #: ../../../docs/configuring-playbook-user-verification-service.md:127
  164. msgid "TLS Certificate Checking"
  165. msgstr ""
  166. #: ../../../docs/configuring-playbook-user-verification-service.md:129
  167. msgid "If the Matrix Homeserver does not provide a valid TLS certificate, UVS will fail with the following error message:"
  168. msgstr ""
  169. #: ../../../docs/configuring-playbook-user-verification-service.md:131
  170. msgid "message: 'No response received: [object Object]',"
  171. msgstr ""
  172. #: ../../../docs/configuring-playbook-user-verification-service.md:133
  173. msgid "This also applies to self-signed and Let's Encrypt staging certificates."
  174. msgstr ""
  175. #: ../../../docs/configuring-playbook-user-verification-service.md:135
  176. msgid "To disable certificate validation altogether (INSECURE! Not suitable for production use!) set: `NODE_TLS_REJECT_UNAUTHORIZED=0`"
  177. msgstr ""
  178. #: ../../../docs/configuring-playbook-user-verification-service.md:137
  179. 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."
  180. msgstr ""