This repository has been archived by the owner on Nov 25, 2024. It is now read-only.
-
-
Notifications
You must be signed in to change notification settings - Fork 672
Implement whoami endpoint #404
Comments
(and make sure it works with appservices 😇 ) |
@turt2live Thanks! You think the spec would mention them :P |
I wrote that spec, so that's more of an oversight on my part :( /me scribbles unintelligible words on his todo list |
APwhitehat
added a commit
to APwhitehat/dendrite
that referenced
this issue
Mar 7, 2018
fixes matrix-org#404 Signed-off-by: Anant Prakash <[email protected]>
This is true for most endpoints (and supporting it is not necessarily 'Easy'). We should probably have a separate bug to track it? |
@richvdh Good point, I'll move it out. |
Actually I'm pretty sure it's just tracked under #358. |
3 tasks
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Spec URL: https://matrix.org/docs/spec/client_server/r0.3.0.html#get-matrix-client-r0-account-whoami
Phase: 2
Difficulty: Easy
We receive an access token, and with that we return the user_id connected to that access token.
Summary:
/account/whoami
in routing.goM_UNKNOWN_TOKEN
/account/whoami
with correct and incorrect access tokens.The text was updated successfully, but these errors were encountered: