Clarify that per-request UIA for /login/get_token is an RFC 2119 MUST requirement (#1846)

Signed-off-by: Johannes Marbach <n0-0ne+github@mailbox.org>
pull/1848/head
Johannes Marbach 6 months ago committed by GitHub
parent 1e303b3bbc
commit 5a86e384dd
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194

@ -0,0 +1 @@
Clarify that per-request UIA for /login/get_token is an RFC 2119 MUST requirement.

@ -45,7 +45,7 @@ paths:
intend to log in multiple devices must generate a token for each. intend to log in multiple devices must generate a token for each.
With other User-Interactive Authentication (UIA)-supporting endpoints, servers sometimes do not re-prompt With other User-Interactive Authentication (UIA)-supporting endpoints, servers sometimes do not re-prompt
for verification if the session recently passed UIA. For this endpoint, servers should always re-prompt for verification if the session recently passed UIA. For this endpoint, servers MUST always re-prompt
the user for verification to ensure explicit consent is gained for each additional client. the user for verification to ensure explicit consent is gained for each additional client.
Servers are encouraged to apply stricter than normal rate limiting to this endpoint, such as maximum Servers are encouraged to apply stricter than normal rate limiting to this endpoint, such as maximum

Loading…
Cancel
Save