summary refs log tree commit diff
path: root/synapse/handlers/identity.py (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Use the v2 Identity Service API for lookups (MSC2134 + MSC2140) (#5976)Andrew Morgan2019-09-111-22/+34
| | | | | | | This is a redo of https://github.com/matrix-org/synapse/pull/5897 but with `id_access_token` accepted. Implements [MSC2134](https://github.com/matrix-org/matrix-doc/pull/2134) plus Identity Service v2 authentication ala [MSC2140](https://github.com/matrix-org/matrix-doc/pull/2140). Identity lookup-related functions were also moved from `RoomMemberHandler` to `IdentityHandler`.
* Fix existing v2 identity server calls (MSC2140) (#6013)Andrew Morgan2019-09-111-2/+26
| | | | | | | | | | | | Two things I missed while implementing [MSC2140](https://github.com/matrix-org/matrix-doc/pull/2140/files#diff-c03a26de5ac40fb532de19cb7fc2aaf7R80). 1. Access tokens should be provided to the identity server as `access_token`, not `id_access_token`, even though the homeserver may accept the tokens as `id_access_token`. 2. Access tokens must be sent to the identity server in a query parameter, the JSON body is not allowed. We now send the access token as part of an `Authorization: ...` header, which fixes both things. The breaking code was added in https://github.com/matrix-org/synapse/pull/5892 Sytest PR: https://github.com/matrix-org/sytest/pull/697
* Merge pull request #6011 from matrix-org/anoa/fix_3pid_validationErik Johnston2019-09-101-40/+33
|\ | | | | Use account_threepid_delegate for 3pid validation
| * Add changelogAndrew Morgan2019-09-101-3/+3
| |
| * Use account_threepid_delegate for 3pid validationAndrew Morgan2019-09-101-40/+33
| |
* | Ensure a sid parameter is passed to bind_threepid (#5995)Andrew Morgan2019-09-061-1/+7
|/ | | `sid` is required to be part of `three_pid_creds`. We were 500'ing if it wasn't provided instead of returning `M_MISSING_PARAM`.
* Allow Synapse to send registration emails + choose Synapse or an external ↵Andrew Morgan2019-09-061-42/+136
| | | | | | | | | | | | | | | | 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.
* Switch to using v2 Identity Service APIs other than lookup (MSC 2140) (#5892)Andrew Morgan2019-09-051-41/+119
|
* Add POST /_matrix/client/r0/account/3pid/unbind (MSC2140) (#5980)Andrew Morgan2019-09-051-1/+2
| | | Implements `POST /_matrix/client/r0/account/3pid/unbind` from [MSC2140](https://github.com/matrix-org/matrix-doc/blob/dbkr/tos_2/proposals/2140-terms-of-service-2.md#post-_matrixclientr0account3pidunbind).
* Revert "Use the v2 lookup API for 3PID invites (#5897)" (#5937)Andrew Morgan2019-08-301-13/+0
| | | | | This reverts commit 71fc04069a5770a204c3514e0237d7374df257a8. This broke 3PID invites as #5892 was required for it to work correctly.
* Use the v2 lookup API for 3PID invites (#5897)Andrew Morgan2019-08-281-0/+13
| | | | | | | Fixes https://github.com/matrix-org/synapse/issues/5861 Adds support for the v2 lookup API as defined in [MSC2134](https://github.com/matrix-org/matrix-doc/pull/2134). Currently this is only used for 3PID invites. Sytest PR: https://github.com/matrix-org/sytest/pull/679
* Replace returnValue with return (#5736)Amber Brown2019-07-231-9/+9
|
* TypoBrendan Abolivier2019-07-101-1/+1
|
* Send 3PID bind requests as JSON dataBrendan Abolivier2019-07-101-1/+1
|
* Run Black. (#5482)Amber Brown2019-06-201-82/+50
|
* Add ability to perform password reset via email without trusting the ↵Andrew Morgan2019-06-061-2/+11
| | | | | | | | | | | | 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
* Remove threepid binding if id server returns 400/404/501Erik Johnston2019-04-021-9/+10
|
* Fixup docstringsErik Johnston2019-04-021-2/+4
|
* Allowing specifying IS to use in unbind API.Erik Johnston2019-04-011-5/+8
| | | | | | | | | | By default the homeserver will use the identity server used during the binding of the 3PID to unbind the 3PID. However, we need to allow clients to explicitly ask the homeserver to unbind via a particular identity server, for the case where the 3PID was bound out of band from the homeserver. Implements MSC915.
* For unbind poke IS used during binding of 3PIDErik Johnston2019-04-011-9/+35
| | | | | | | | This changes the behaviour from using the server specified trusted identity server to using the IS that used during the binding of the 3PID, if known. This is the behaviour specified by MSC1915.
* Track IS used to bind 3PIDsErik Johnston2019-04-011-0/+15
| | | | | This will then be used to know which IS to default to when unbinding the threepid.
* sign_request -> build_auth_headers (#4408)Richard van der Hoff2019-01-171-3/+6
| | | | | Just got very confused about the fact that the headers are only an output, not an input.
* Log when we 3pid/unbind request failsErik Johnston2018-08-091-0/+2
|
* Don't fail requests to unbind 3pids for non supporting ID serversErik Johnston2018-08-081-9/+21
| | | | | | | | | | Older identity servers may not support the unbind 3pid request, so we shouldn't fail the requests if we received one of 400/404/501. The request still fails if we receive e.g. 500 responses, allowing clients to retry requests on transient identity server errors that otherwise do support the API. Fixes #3661
* Kill off MatrixCodeMessageExceptionRichard van der Hoff2018-08-011-17/+8
| | | | | | | | | | | This code brings the SimpleHttpClient into line with the MatrixFederationHttpClient by having it raise HttpResponseExceptions when a request fails (rather than trying to parse for matrix errors and maybe raising MatrixCodeMessageException). Then, whenever we were checking for MatrixCodeMessageException and turning them into SynapseErrors, we now need to check for HttpResponseExceptions and call to_synapse_error.
* run isortAmber Brown2018-07-091-2/+5
|
* Attempt to be more performant on PyPy (#3462)Amber Brown2018-06-281-1/+1
|
* Remove run_on_reactor (#3395)Amber Brown2018-06-141-8/+0
|
* doc fixesDavid Baker2018-06-051-1/+1
|
* docstringDavid Baker2018-06-041-1/+9
|
* pep8David Baker2018-05-241-3/+4
|
* commentDavid Baker2018-05-241-0/+4
|
* Hit the 3pid unbind endpoint on deactivationDavid Baker2018-05-231-0/+35
|
* Use simplejson throughoutRichard van der Hoff2018-03-291-3/+5
| | | | Let's use simplejson rather than json, for consistency.
* Revert accidental commitDavid Baker2017-04-261-4/+4
|
* Use CodeMessageException subclass insteadDavid Baker2017-04-251-10/+19
| | | | | Parse json errors from get_json client methods and throw special errors.
* Propagate errors sensibly from proxied IS requestsDavid Baker2017-04-211-5/+5
| | | | | | When we're proxying Matrix endpoints, parse out Matrix error responses and turn them into SynapseErrors so they can be propagated sensibly upstream.
* Support registration / login with phone numberDavid Baker2017-03-131-1/+36
| | | | Changes from https://github.com/matrix-org/synapse/pull/1971
* Revert "Support registration & login with phone number"Erik Johnston2017-03-131-36/+1
|
* WIP support for msisdn 3pid proxy methodsDavid Baker2017-02-141-1/+36
|
* requestToken updateDavid Baker2016-06-301-14/+27
| | | | | | Don't send requestToken request to untrusted ID servers Also correct the THREEPID_IN_USE error to add the M_ prefix. This is a backwards incomaptible change, but the only thing using this is the angular client which is now unmaintained, so it's probably better to just do this now.
* Add missing param to the log lineMark Haines2016-01-291-1/+2
|
* Add config option for setting the trusted id servers, disabling checking the ↵Mark Haines2016-01-291-8/+17
| | | | ID server in integration tests
* copyrightsMatthew Hodgson2016-01-071-1/+1
|
* Reuse a single http client, rather than creating new onesMark Haines2015-12-021-9/+5
|
* Add endpoint that proxies ID server request token and errors if the given ↵David Baker2015-08-041-0/+25
| | | | email is in use on this Home Server.
* Add vector.im as trusted ID serverDavid Baker2015-08-031-1/+1
|
* Accept camelcase + underscores in binding tooDavid Baker2015-04-291-2/+17
|
* Fix includesDavid Baker2015-04-291-1/+2
|
* Accept both camelcase and underscore threepid creds for transitionDavid Baker2015-04-291-4/+19
|
* Change to https for ID server communicationDavid Baker2015-04-241-3/+2
|
* Use underscores instead of camelcase for id server stuffDavid Baker2015-04-241-6/+6
|
* pep8David Baker2015-04-171-3/+3
|
* Return user ID in use error straight awayDavid Baker2015-04-161-1/+24
|
* Dummy login so we can do the first POST request to get login flows without ↵David Baker2015-04-151-3/+3
| | | | it just succeeding
* Regstration with email in v2David Baker2015-04-151-0/+66
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-11-18 14:20:28 +0000