webpush-wg webpush-vapid issues

webpush-wg / webpush-vapid

Voluntary application server self-identification for web push

3 stars 2 forks source link

issues

Newest

Newest Most commented Recently updated Oldest Least commented Least recently updated

For Ben

#44 martinthomson closed 7 years ago
0
For @ekr

#43 martinthomson closed 7 years ago
1
Add a challenge

#42 martinthomson closed 7 years ago
0
For Kathleen

#41 martinthomson closed 7 years ago
0
Why limit expiration

#40 martinthomson closed 7 years ago
0
User agents create subscriptions, not application servers

#39 martinthomson closed 7 years ago
0
Typo fix: optjons -> options

#38 beverloo closed 7 years ago
0
Adam's nits

#37 martinthomson closed 7 years ago
1
Change keys gradually

#36 martinthomson closed 7 years ago
0
Document the plan for cryptographic agility

#35 martinthomson closed 7 years ago
0
Define a media type for the options

#34 martinthomson closed 7 years ago
0
Describe key rollover

#33 martinthomson closed 7 years ago
0
Shepherd review nits

#32 PSUdaemon closed 7 years ago
0
Use JSON to restrict subscriptions

#31 martinthomson closed 7 years ago
4
Let other use this if it suits.

#30 martinthomson closed 7 years ago
1
Unified auth scheme

#29 martinthomson closed 7 years ago
3
Move public key to the authorization header field

#28 martinthomson closed 7 years ago
1
Let the user agent authenticate using VAPID too.

#27 martinthomson closed 7 years ago
0
Some minor quibbles and two questions

#26 x3ro closed 8 years ago
2
Adding a section on additional claims

#25 martinthomson closed 7 years ago
4
VAPID claim should include optional extra data field

#24 jrconlin closed 7 years ago
1
"aud" URL needs to be clarified

#23 jrconlin closed 8 years ago
9
Refer to `dh` in the note rather than `p256dh`

#22 beverloo closed 8 years ago
0
Clean up references to "token"

#21 martinthomson closed 8 years ago
0
We aren't going to allow dropping of the JWT header

#20 martinthomson closed 8 years ago
0
Make it clearer what the example JWT relates to

#19 martinthomson closed 8 years ago
0
Correcting example auth scheme name

#18 martinthomson closed 8 years ago
0
Bearer

#17 martinthomson closed 8 years ago
1
Removing wishy-washy regarding key generation

#16 martinthomson closed 8 years ago
0
an AS no longer subscribes

#15 martinthomson closed 8 years ago
2
Editorial changes

#14 brianraymor closed 8 years ago
0
5.2 Using Restricted Subscriptions: References to "token"

#13 brianraymor closed 8 years ago
1
2.2 Example: JWT and "that segment"

#12 brianraymor closed 8 years ago
3
2.2 Example: This equates to a JWT with the header and body shown in Figure 2.

#11 brianraymor closed 8 years ago
0
2.2 Example: Authorization header

#10 brianraymor closed 8 years ago
2
Application servers SHOULD generate and maintain a signing key pair

#9 brianraymor closed 8 years ago
0
Updates required when webpush-05 is published

#8 brianraymor closed 8 years ago
0
Fix auth scheme name in example

#7 ghost closed 8 years ago
2
Reject silliness with identical ecdsa and ecdh keys

#6 martinthomson closed 8 years ago
0
Sec 5.2 is contradictory

#5 jrconlin closed 8 years ago
1
Change draft to concentrate on JWT option only

#4 martinthomson closed 8 years ago
7
Association Take 2

#3 martinthomson closed 8 years ago
1
Adding JWT option, rearranging

#2 martinthomson closed 8 years ago
0
First attempt for subscription association

#1 beverloo closed 8 years ago
3