summary refs log tree commit diff
path: root/synapse/res (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Allow HS to send emails when adding an email to the HS (#6042)Andrew Morgan2019-09-204-0/+29
|
* Allow Synapse to send registration emails + choose Synapse or an external ↵Andrew Morgan2019-09-067-4/+39
| | | | | | | | | | | | | | | | server to handle 3pid validation (#5987) This is a combination of a few different PRs, finally all being merged into `develop`: * #5875 * #5876 * #5868 (This one added the `/versions` flag but the flag itself was actually [backed out](https://github.com/matrix-org/synapse/commit/891afb57cbdf9867f2848341b29c75d6f35eef5a#diff-e591d42d30690ffb79f63bb726200891) in #5969. What's left is just giving /versions access to the config file, which could be useful in the future) * #5835 * #5969 * #5940 Clients should not actually use the new registration functionality until https://github.com/matrix-org/synapse/pull/5972 is merged. UPGRADE.rst, changelog entries and config file changes should all be reviewed closely before this PR is merged.
* Allow defining HTML templates to serve the user on account renewalBrendan Abolivier2019-08-012-0/+2
|
* Change password reset links to /_matrix.Erik Johnston2019-06-111-1/+1
|
* Add ability to perform password reset via email without trusting the ↵Andrew Morgan2019-06-064-0/+28
| | | | | | | | | | | | identity server (#5377) Sends password reset emails from the homeserver instead of proxying to the identity server. This is now the default behaviour for security reasons. If you wish to continue proxying password reset requests to the identity server you must now enable the email.trust_identity_server_for_password_resets option. This PR is a culmination of 3 smaller PRs which have each been separately reviewed: * #5308 * #5345 * #5368
* Send out emails with links to extend an account's validity periodBrendan Abolivier2019-04-173-0/+54
|
* Use static locations for Riot iconsTravis Ralston2019-03-013-7/+7
| | | See https://github.com/vector-im/riot-web/issues/9009
* Ship the email templates as package_dataRichard van der Hoff2018-10-178-0/+331
move the example email templates into the synapse package so that they can be used as package data, which should mean that all of the packaging mechanisms (pip, docker, debian, arch, etc) should now come with the example templates. In order to grandfather in people who relied on the templates being in the old place, check for that situation and fall back to using the defaults if the templates directory does not exist.