Skip to content
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

Document access_token in headers #1042

Closed
t3chguy opened this issue Oct 26, 2017 · 3 comments
Closed

Document access_token in headers #1042

t3chguy opened this issue Oct 26, 2017 · 3 comments
Labels
spec-omission implemented but not currently specified

Comments

@t3chguy
Copy link
Member

t3chguy commented Oct 26, 2017

No description provided.

@richvdh
Copy link
Member

richvdh commented Oct 26, 2017

You can now (as of matrix-org/synapse#1098) put your access token in an Auth header instead. We should spec it.

@richvdh
Copy link
Member

richvdh commented Oct 27, 2017

I don't really feel this is adequately documented yet. It's nice to have it mentioned in the spec but we need to be clearer about how clients use it, and that servers must provide it.

@richvdh richvdh reopened this Oct 27, 2017
@turt2live
Copy link
Member

@richvdh the section feels fairly clear to me - what kind of improvement were you thinking of?

for reference:

Most API endpoints require the user to identify themselves by presenting
previously obtained credentials in the form of an access_token query
parameter or through an Authorization Header of Bearer $access_token.
An access token is typically obtained via the Login_ or Registration_ processes.

@turt2live turt2live added this to To do: client-server (prioritized) in August 2018 r0 Aug 14, 2018
turt2live added a commit to turt2live/matrix-doc that referenced this issue Aug 15, 2018
@turt2live turt2live moved this from To do: client-server (prioritized) to In review in August 2018 r0 Aug 15, 2018
August 2018 r0 automation moved this from In review to Done (this list will be incomplete) Aug 20, 2018
RiotTranslateBot pushed a commit to RiotTranslateBot/matrix-doc that referenced this issue Aug 22, 2023
* Opinionated rewrite of unconflicted state map

* Define auth chain
RiotTranslateBot pushed a commit to RiotTranslateBot/matrix-doc that referenced this issue Aug 22, 2023
In matrix-org#1042 I incorrectly wrote that the conflicted state set is a set of
pairs (K, V). We later take the union of the conflicted state set and
the auth difference. The latter is a set of events (V) only.

Fix this by making the conflicted state set a set of events rather than
a set of pairs. That is, the conflicted state set is a a `Set[Event]`
instead of a `Set[((type, state key), event)]`.
RiotTranslateBot pushed a commit to RiotTranslateBot/matrix-doc that referenced this issue Aug 22, 2023
…g#1158)

* Fix unintentional stateres change added in matrix-org#1042

* Changelog
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
spec-omission implemented but not currently specified
Projects
No open projects
August 2018 r0
  
Done (this list will be incomplete)
Development

No branches or pull requests

3 participants