Skip to content
Snippets Groups Projects
  1. Feb 14, 2022
  2. Feb 11, 2022
  3. Feb 10, 2022
  4. Feb 09, 2022
  5. Feb 08, 2022
  6. Feb 04, 2022
  7. Feb 03, 2022
  8. Jan 31, 2022
  9. Jan 28, 2022
  10. Jan 27, 2022
  11. 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
  12. Jan 25, 2022
  13. Jan 24, 2022
  14. Jan 21, 2022
    • Shay's avatar
      Drop support for and remove references to EOL Python 3.6 (#11683) · 9006ee36
      Shay authored
      * remove reference in comments to python3.6
      
      * upgrade tox python env in script
      
      * bump python version in example for completeness
      
      * upgrade python version requirement in setup doc
      
      * upgrade necessary python version in __init__.py
      
      * upgrade python version in setup.py
      
      * newsfragment
      
      * drops refs to bionic and replace with focal
      
      * bump refs to postgres 9.6 to 10
      
      * fix hanging ci
      
      * try installing tzdata first
      
      * revert change made in b979f336
      
      * ignore new random mypy error while debugging other error
      
      * fix lint error for temporary workaround
      
      * revert change to install list
      
      * try passing env var
      
      * export debian frontend var?
      
      * move line and add comment
      
      * bump pillow dependency
      
      * bump lxml depenency
      
      * install libjpeg-dev for pillow
      
      * bump automat version to one compatible with py3.8
      
      * add libwebp for pillow
      
      * bump twisted trunk python version
      
      * change suffix of newsfragment
      
      * remove redundant python 3.7 checks
      
      * lint
      9006ee36
  15. Jan 20, 2022
  16. Jan 18, 2022
  17. Jan 17, 2022
  18. Jan 14, 2022
  19. Jan 13, 2022
  20. Jan 12, 2022
    • Jason Robinson's avatar
      Allow tracking puppeted users for MAU (#11561) · 2560b1b6
      Jason Robinson authored
      
      Currently when puppeting another user, the user doing the puppeting is
      tracked for client IPs and MAU (if configured).
      
      When tracking MAU is important, it becomes necessary to be possible to
      also track the client IPs and MAU of puppeted users. As an example a
      client that manages user creation and creation of tokens via the Synapse
      admin API, passing those tokens for the client to use.
      
      This PR adds optional configuration to enable tracking of puppeted users
      into monthly active users. The default behaviour stays the same.
      
      Signed-off-by: default avatarJason Robinson <jasonr@matrix.org>
      2560b1b6
Loading