Apply suggestions from code review
Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
This commit is contained in:
parent
91b2a49b6f
commit
ef3df9d549
4 changed files with 6 additions and 6 deletions
|
@ -391,8 +391,8 @@ should be used when the access token needs to be refreshed.
|
||||||
|
|
||||||
The old refresh token remains valid until the new access token or refresh token
|
The old refresh token remains valid until the new access token or refresh token
|
||||||
is used, at which point the old refresh token is revoked. This ensures that if
|
is used, at which point the old refresh token is revoked. This ensures that if
|
||||||
a client fails to receive or persist the new tokens, it will still be able to
|
a client fails to receive or persist the new tokens, it will be able to repeat
|
||||||
refresh them.
|
the refresh operation.
|
||||||
|
|
||||||
If the token refresh fails and the error response included a `soft_logout:
|
If the token refresh fails and the error response included a `soft_logout:
|
||||||
true` property, then the client can treat it as a [soft logout](#soft-logout)
|
true` property, then the client can treat it as a [soft logout](#soft-logout)
|
||||||
|
|
|
@ -184,7 +184,7 @@ paths:
|
||||||
The lifetime of the access token, in milliseconds. Once
|
The lifetime of the access token, in milliseconds. Once
|
||||||
the access token has expired a new access token can be
|
the access token has expired a new access token can be
|
||||||
obtained by using the provided refresh token. If no
|
obtained by using the provided refresh token. If no
|
||||||
refresh token is provided, the client will need re-log in
|
refresh token is provided, the client will need to re-log in
|
||||||
to obtain a new access token. If not given, the client can
|
to obtain a new access token. If not given, the client can
|
||||||
assume that the access token will not expire.
|
assume that the access token will not expire.
|
||||||
x-addedInMatrixVersion: "1.3"
|
x-addedInMatrixVersion: "1.3"
|
||||||
|
|
|
@ -45,8 +45,8 @@ paths:
|
||||||
The old refresh token remains valid until the new access token or refresh token
|
The old refresh token remains valid until the new access token or refresh token
|
||||||
is used, at which point the old refresh token is revoked.
|
is used, at which point the old refresh token is revoked.
|
||||||
|
|
||||||
Note that this endpoint does not require authentication, since
|
Note that this endpoint does not require authentication via an
|
||||||
authentication is provided via the refresh token.
|
access token. Authentication is provided via the refresh token.
|
||||||
|
|
||||||
Application Service identity assertion is disabled for this endpoint.
|
Application Service identity assertion is disabled for this endpoint.
|
||||||
operationId: refresh
|
operationId: refresh
|
||||||
|
|
|
@ -173,7 +173,7 @@ paths:
|
||||||
The lifetime of the access token, in milliseconds. Once
|
The lifetime of the access token, in milliseconds. Once
|
||||||
the access token has expired a new access token can be
|
the access token has expired a new access token can be
|
||||||
obtained by using the provided refresh token. If no
|
obtained by using the provided refresh token. If no
|
||||||
refresh token is provided, the client will need re-log in
|
refresh token is provided, the client will need to re-log in
|
||||||
to obtain a new access token. If not given, the client can
|
to obtain a new access token. If not given, the client can
|
||||||
assume that the access token will not expire.
|
assume that the access token will not expire.
|
||||||
|
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue