-
Notifications
You must be signed in to change notification settings - Fork 16
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
doc: Update docs to indicate that
sub
is required. (#758)
We require the `sub` so that we can contact folk that are possibly doing questionable things. While we don't validate the contact URI, if we see a problem and we can't contact folk, it probably means we're just going to block them. Closes #SYNC-3678
- Loading branch information
Showing
2 changed files
with
18 additions
and
2 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -253,10 +253,18 @@ An example of the Authorization header would be: | |
_The [VAPID Key](https://datatracker.ietf.org/doc/html/rfc8292#section-3.2) provided by the subscribing third party_ | ||
|
||
The VAPID key is optional and provides a way for an application server to voluntarily identify itself. | ||
When the VAPID key is provided, autopush will return an endpoint that can only be used by the application server that provided the key. | ||
**The VAPID key is formatted as a URL-safe Base64 encoded string with no padding.** | ||
|
||
_*Please Note*_: While the VAPID key is optional, if it is included, the VAPID asserion block _must_ contain a `sub` field containing the publishing contact information as a vaild URI designator. (e.g. `mailto:[email protected]` or `https://example.org/contact`). As an example, a minimal VAPID assertion block would contain: | ||
|
||
```json | ||
{"aud": "https://updates.push.services.mozilla.com", "exp": 1725468595, "sub": "mailto:[email protected]"} | ||
``` | ||
|
||
Where `exp` and `sub` reflect the expiration time and publishing contact information. The contact information is used in case of an issue with use of the Push service and is never used for marketing purposes. | ||
|
||
When the VAPID key is provided, autopush will return an endpoint that can only be used by the application server that provided the key. | ||
|
||
**The VAPID key is formatted as a URL-safe Base64 encoded string with no padding.** | ||
|
||
## Calls | ||
|
||
|