Skip to content

Allow signed challenge caching and recommend challenge lifetime #233

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.

Sign up for GitHub

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
+5 −1
Open

Allow signed challenge caching and recommend challenge lifetime #233

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion spec.bs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -308,6 +308,9 @@ register a session on the Relying Party (RP) with new keys. Therefore RPs should
only accept sessions registered with the appropriate public keys they received
from the SP.

New challenges issued should have a short lifetime. The server should reject
signed responses that use a stale challenge.

# User agent considerations # {#user-agent-considerations}

DBSC provides a lot of flexibility for browsers to schedule cookie
Expand Down Expand Up @@ -630,7 +633,8 @@ both `example.co.uk` and `www.example.de` is `example`.
non-null, let |session response| be the result of creating a [=DBSC proof=]
for |challenge| and |authorization|.
1. If |key pair| and |session response| are non-null, sign |session response|
with |key pair|.
with |key pair|. The user agent MAY reuse cached results from a previous signing
if all inputs are the same instead of resigning.
1. Create a |request| for use in <a
href="https://fetch.spec.whatwg.org/#http-fetch">HTTP fetch</a>.
1. Set |request|'s [=request/method=] to "POST".
Expand Down