Reword "UI Authorization" to "User-Interactive Authentication" (#2667)

Signed-off-by: Aaron Raimist <aaron@raim.ist>
pull/977/head
Aaron Raimist 4 years ago committed by GitHub
parent a91c6446bc
commit f8ff2ad6a9
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

@ -54,11 +54,12 @@ paths:
for the user are also deleted. `Device keys <#device-keys>`_ for the device are
deleted alongside the device.
This endpoint does not require UI authorization because UI authorization is
designed to protect against attacks where the someone gets hold of a single access
token then takes over the account. This endpoint invalidates all access tokens for
the user, including the token used in the request, and therefore the attacker is
unable to take over the account in this way.
This endpoint does not use the `User-Interactive Authentication API`_ because
User-Interactive Authentication is designed to protect against attacks where the
someone gets hold of a single access token then takes over the account. This
endpoint invalidates all access tokens for the user, including the token used in
the request, and therefore the attacker is unable to take over the account in
this way.
operationId: logout_all
security:
- accessToken: []

@ -0,0 +1 @@
Reword "UI Authorization" to "User-Interactive Authentication" to be more clear.

@ -1090,8 +1090,7 @@ Login
A client can obtain access tokens using the ``/login`` API.
Note that this endpoint does `not` currently use the user-interactive
authentication API.
Note that this endpoint does `not` currently use the `User-Interactive Authentication API`_.
For a simple username/password login, clients should submit a ``/login``
request as follows:

Loading…
Cancel
Save