summary refs log tree commit diff
path: root/tests/rest/client/v1/test_profile.py (follow)
Commit message (Collapse)AuthorAgeFilesLines
* LintBrendan Abolivier2019-07-081-2/+2
|
* Add test caseBrendan Abolivier2019-07-081-0/+47
|
* Run Black. (#5482)Amber Brown2019-06-201-4/+3
|
* Unify v1 and v2 REST client APIs (#5226)Amber Brown2019-06-031-1/+1
|
* add some testsRichard van der Hoff2019-06-011-2/+60
|
* Migrate all tests to use the dict-based config format instead of hanging ↵Amber Brown2019-05-131-1/+1
| | | | items off HomeserverConfig (#5171)
* Run Black on the tests again (#5170)Amber Brown2019-05-101-21/+6
|
* Fix bogus imports in tests (#5154)Brendan Abolivier2019-05-081-2/+3
|
* add options to require an access_token to GET /profile and /publicRooms on ↵Matthew Hodgson2019-05-081-1/+91
| | | | | | | | | | | | | | | | | CS API (#5083) This commit adds two config options: * `restrict_public_rooms_to_local_users` Requires auth to fetch the public rooms directory through the CS API and disables fetching it through the federation API. * `require_auth_for_profile_requests` When set to `true`, requires that requests to `/profile` over the CS API are authenticated, and only returns the user's profile if the requester shares a room with the profile's owner, as per MSC1301. MSC1301 also specifies a behaviour for federation (only returning the profile if the server asking for it shares a room with the profile's owner), but that's currently really non-trivial to do in a not too expensive way. Next step is writing down a MSC that allows a HS to specify which user sent the profile query. In this implementation, Synapse won't send a profile query over federation if it doesn't believe it already shares a room with the profile's owner, though. Groups have been intentionally omitted from this commit.
* Run tests under PostgreSQL (#3423)Amber Brown2018-08-131-0/+1
|
* Run black.black2018-08-101-23/+19
|
* Test fixes for Python 3 (#3647)Amber Brown2018-08-091-4/+4
|
* run isortAmber Brown2018-07-091-1/+4
|
* Burminate v1authAdrian Tschira2018-04-301-1/+1
| | | | | | | | | | | | | | | | | | This closes #2602 v1auth was created to account for the differences in status code between the v1 and v2_alpha revisions of the protocol (401 vs 403 for invalid tokens). However since those protocols were merged, this makes the r0 version/endpoint internally inconsistent, and violates the specification for the r0 endpoint. This might break clients that rely on this inconsistency with the specification. This is said to affect the legacy angular reference client. However, I feel that restoring parity with the spec is more important. Either way, it is critical to inform developers about this change, in case they rely on the illegal behaviour. Signed-off-by: Adrian Tschira <nota@notafile.com>
* s/replication_client/federation_client/Erik Johnston2018-03-131-1/+1
|
* Fix testsErik Johnston2018-03-131-1/+1
|
* Split out profile handler to fix testsErik Johnston2017-08-251-2/+1
|
* Add `create_requester` functionRichard van der Hoff2016-07-261-8/+5
| | | | | Wrap the `Requester` constructor with a function which provides sensible defaults, and use it throughout
* Use parse_json_object_from_request to parse JSON out of request bodiesMark Haines2016-03-111-2/+4
|
* Pass whole requester to ratelimitingDaniel Wagner-Hall2016-03-031-2/+2
| | | | This will enable more detailed decisions
* Fix flake8 warnings for testsMark Haines2016-02-191-22/+34
|
* Introduce a Requester objectDaniel Wagner-Hall2016-01-111-4/+3
| | | | | | | | | This tracks data about the entity which made the request. This is instead of passing around a tuple, which requires call-site modifications every time a new piece of optional context is passed around. I tried to introduce a User object. I gave up.
* copyrightsMatthew Hodgson2016-01-071-1/+1
|
* Allow guests to register and call /events?room_id=Daniel Wagner-Hall2015-11-041-2/+2
| | | | | | | This follows the same flows-based flow as regular registration, but as the only implemented flow has no requirements, it auto-succeeds. In the future, other flows (e.g. captcha) may be required, so clients should treat this like the regular registration flow choices.
* Fix testsDavid Baker2015-03-241-1/+1
|
* Factor out some of the common homeserver setup code into aMark Haines2015-02-111-9/+4
| | | | setup_test_homeserver function in utils.
* Return the device_id from get_auth_by_reqMark Haines2015-01-281-1/+1
|
* Replace hs.parse_userid with UserID.from_stringMark Haines2015-01-231-1/+2
|
* Merge rest servlets into the client json resource objectMark Haines2015-01-231-1/+3
|
* Move client rest tests back under restMark Haines2015-01-221-0/+150
generated by cgit-pink 1.4.1 (git 2.36.1) at 2024-11-24 02:48:46 +0000