Minor typo and formatting fixes
This commit is contained in:
parent
1abb82d6e0
commit
0341c30824
2 changed files with 3 additions and 3 deletions
|
@ -1,7 +1,7 @@
|
||||||
Macaroon Caveats
|
Macaroon Caveats
|
||||||
================
|
================
|
||||||
|
|
||||||
Macaroons (http://theory.stanford.edu/~ataly/Papers/macaroons.pdf) are issued by Matrix servers as authorization tokens. Macaroons may be restricted, by adding caveats to them.
|
Macaroons (http://theory.stanford.edu/~ataly/Papers/macaroons.pdf) are issued by Matrix servers as authorization tokens. Macaroons may be restricted by adding caveats to them.
|
||||||
|
|
||||||
Caveats can only be used for reducing the scope of a token, never for increasing it. Servers are required to reject any macroon with a caveat that they do not understand.
|
Caveats can only be used for reducing the scope of a token, never for increasing it. Servers are required to reject any macroon with a caveat that they do not understand.
|
||||||
|
|
||||||
|
|
|
@ -1035,7 +1035,7 @@ user_id
|
||||||
The fully-qualified Matrix ID that has been registered.
|
The fully-qualified Matrix ID that has been registered.
|
||||||
access_token
|
access_token
|
||||||
An access token for the account. This token may expire at some point, and if
|
An access token for the account. This token may expire at some point, and if
|
||||||
so, it MAY come with a refersh_token, described below.
|
so, it MAY come with a refresh_token, described below.
|
||||||
refresh_token (optional)
|
refresh_token (optional)
|
||||||
A refresh token may be exchanged for a new access_token as described in
|
A refresh token may be exchanged for a new access_token as described in
|
||||||
`Refreshing access tokens`.
|
`Refreshing access tokens`.
|
||||||
|
@ -1064,7 +1064,7 @@ refresh_token (optional)
|
||||||
There is no specific error message to indicate that a request has failed because
|
There is no specific error message to indicate that a request has failed because
|
||||||
an access token has expired; instead, if a client has reason to believe its
|
an access token has expired; instead, if a client has reason to believe its
|
||||||
access token is valid, and it receives an auth error, they should attempt to
|
access token is valid, and it receives an auth error, they should attempt to
|
||||||
refresh for a new token on failure, and re-try the request with the new token.
|
refresh for a new token on failure, and retry the request with the new token.
|
||||||
|
|
||||||
Changing Password
|
Changing Password
|
||||||
~~~~~~~~~~~~~~~~~
|
~~~~~~~~~~~~~~~~~
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue