-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Have the in-built identity server support v2 #689
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this looks generally good, modulo a few nits.
Factoring out each endpoint to its own function is a great idea, but the diff would have been an order of magnitude clearer (and hence it would be easier to review) if the refactor had been in a separate PR to the new functionality...
Added docstrings for every function. |
…ase-v1.4.0 * origin/release-v1.4.0: (36 commits) Improve logging for a failing test (#709) Make 3PID binding tests use /account/3pid/bind ala MSC2290 (#703) Use unstable prefix for 3PID unbind API Add support for handling email validation challenges (#707) do requestToken before adding a 3pid (#706) Configure synapse to use the test mail server (#705) Implement a mail server to help with 3pid testing (#704) federated_rooms_fixture (#701) Use Sytest develop for Dendrite's master branch (#700) Don't assume atomicity Fix flakiness due to create_room_synced (#702) Don't require an avatar_url Replace HOMESERVER_INFO incantations (#699) add some logging for flaky sync test (#698) Fix problems when using hash Accept access_token instead of id_access_token on the IS, accept Authorization header (#697) Use hash and handle variable sized final chunk Have the in-built identity server support v2 (#689) Add tests for 3PID /unbind API (#691) Fix typo ...
Add all of the v2 identity server endpoints to Sytest's built-in identity server. This is independent of any of the Synapse changes currently in-flight.
Additionally, change the identity server tests to use these v2 endpoints.
This essentially just involves switching the endpoints to v2 and including an
id_access_token
parameter at the top-level of the JSON, or in a query parameter. I tried to reuse functions wherever possible.The
id_access_token
is hard-coded, as there isn't much point retrieving it via OpenID as we're using a built-in Sytest identity server, which we don't need to test. Sydent's OpenID functionality is handled by matrix-is-tester.