You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 13, 2023. It is now read-only.
Continuing the work of #325, clients can provide a Public Key as part of the register() call.
Incoming subscription update requests (Crypto-Key Header; p256ecdsa component) must match the registered key.
Requests that do not match shall be rejected with a 401.
Requests that use the same public key for p256ecdsa and dh components shall be rejected with a 400.
It has been suggested that a hash of the public key be stored in the endpoint, which may require endpoint versioning.
The text was updated successfully, but these errors were encountered:
Continuing the work of #325, clients can provide a Public Key as part of the register() call.
Incoming subscription update requests (Crypto-Key Header; p256ecdsa component) must match the registered key.
Requests that do not match shall be rejected with a 401.
Requests that use the same public key for p256ecdsa and dh components shall be rejected with a 400.
It has been suggested that a hash of the public key be stored in the endpoint, which may require endpoint versioning.
The text was updated successfully, but these errors were encountered: