Skip to content
Snippets Groups Projects
  1. Mar 08, 2022
    • Patrick Cloke's avatar
      Clean-up demo scripts & documentation (#12143) · 9a0172d4
      Patrick Cloke authored
      * Rewrites the demo documentation to be clearer, accurate, and moves it to our documentation tree.
      * Improvements to the demo scripts:
      	* `clean.sh` now runs `stop.sh` first to avoid zombie processes.
      	* Uses more modern Synapse configuration (and removes some obsolete configuration).
      	* Consistently use the HTTP ports for server name, etc.
      	* Remove the `demo/etc` directory and place everything into the `demo/808x` directories.
      9a0172d4
  2. Mar 04, 2022
  3. Mar 02, 2022
  4. Mar 01, 2022
  5. Feb 28, 2022
    • Patrick Cloke's avatar
      Remove the unstable `/spaces` endpoint. (#12073) · 7754af24
      Patrick Cloke authored
      ...and various code supporting it.
      
      The /spaces endpoint was from an old version of MSC2946 and included
      both a Client-Server and Server-Server API. Note that the unstable
      /hierarchy endpoint (from the final version of MSC2946) is not yet
      removed.
      7754af24
  6. Feb 23, 2022
  7. Feb 22, 2022
  8. Feb 18, 2022
  9. Feb 17, 2022
  10. Feb 16, 2022
  11. Feb 14, 2022
  12. Feb 11, 2022
  13. Feb 10, 2022
  14. Feb 09, 2022
  15. Feb 08, 2022
  16. Feb 04, 2022
  17. Feb 03, 2022
  18. Jan 31, 2022
  19. Jan 28, 2022
  20. Jan 27, 2022
  21. Jan 26, 2022
    • Brendan Abolivier's avatar
      Add a module callback to set username at registration (#11790) · 2d3bd9aa
      Brendan Abolivier authored
      
      This is in the context of mainlining the Tchap fork of Synapse. Currently in Tchap usernames are derived from the user's email address (extracted from the UIA results, more specifically the m.login.email.identity step).
      This change also exports the check_username method from the registration handler as part of the module API, so that a module can check if the username it's trying to generate is correct and doesn't conflict with an existing one, and fallback gracefully if not.
      
      Co-authored-by: default avatarDavid Robertson <davidr@element.io>
      2d3bd9aa
    • Brendan Abolivier's avatar
      Add a config flag to inhibit `M_USER_IN_USE` during registration (#11743) · 95b3f952
      Brendan Abolivier authored
      This is mostly motivated by the tchap use case, where usernames are automatically generated from the user's email address (in a way that allows figuring out the email address from the username). Therefore, it's an issue if we respond to requests on /register and /register/available with M_USER_IN_USE, because it can potentially leak email addresses (which include the user's real name and place of work).
      
      This commit adds a flag to inhibit the M_USER_IN_USE errors that are raised both by /register/available, and when providing a username early into the registration process. This error will still be raised if the user completes the registration process but the username conflicts. This is particularly useful when using modules (https://github.com/matrix-org/synapse/pull/11790 adds a module callback to set the username of users at registration) or SSO, since they can ensure the username is unique.
      
      More context is available in the PR that introduced this behaviour to synapse-dinsic: matrix-org/synapse-dinsic#48 - as well as the issue in the matrix-dinsic repo: matrix-org/matrix-dinsic#476
      95b3f952
  22. Jan 25, 2022
Loading