Search results

Why is session expiration updated during refresh lookup in section 8.5?

Status: Open.

#204 In w3c/webappsec-dbsc;

· ynojima opened on Jul 19, 2025

Use more standard claims for <code>/securesession/startsession</code> and <code>/securesession/refresh</code> and don't provide the public key in the refresh endpoint

Status: Open.

#201 In w3c/webappsec-dbsc;

· arianvp opened on Jul 8, 2025

iat is a number and jwk is json

Status: Open.

#178 In w3c/webappsec-dbsc;

· bc-pi opened on May 12, 2025

JS bindings for usage of session keys

Status: Open.

#177 In w3c/webappsec-dbsc;

· drubery opened on May 12, 2025

JS bindings for session registration

Status: Open.

#176 In w3c/webappsec-dbsc;

· drubery opened on May 12, 2025

Consider Renaming "Device Bound Session Credentials" for Clarity

Status: Open.

#152 In w3c/webappsec-dbsc;

· kkoiwai opened on Apr 24, 2025

Synchronous operation and capability discovery

Status: Open.

#117 In w3c/webappsec-dbsc;

· sbweeden opened on Mar 17, 2025

HTTP Message Signatures

Status: Open.

#112 In w3c/webappsec-dbsc;

· jricher opened on Mar 5, 2025

Need for attestation?

Status: Open.

#34 In w3c/webappsec-dbsc;

· jackevans43 opened on Apr 7, 2024

timed refresh mechanism

Status: Open.

#33 In w3c/webappsec-dbsc;

· dickhardt opened on Apr 6, 2024

alignment with OAuth 2 flows for 1P authorization servers

Status: Open.

#31 In w3c/webappsec-dbsc;

· dickhardt opened on Apr 6, 2024

Question RE: Tracking and Identity Providers

Status: Open.

#24 In w3c/webappsec-dbsc;

· whitehatguy opened on Apr 4, 2024