Skip to content
This repository has been archived by the owner on Jul 13, 2023. It is now read-only.

Provide Public Key Registration for VAPID #337

Closed
jrconlin opened this issue Feb 11, 2016 · 1 comment
Closed

Provide Public Key Registration for VAPID #337

jrconlin opened this issue Feb 11, 2016 · 1 comment

Comments

@jrconlin
Copy link
Member

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.

@jrconlin
Copy link
Member Author

closing as duplicate of #326

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant