Zapp apps provides you the ability to used signed URL prior to playback.
Using signed URLs help you protect your content and prevent unauthorized viewers from viewing or downloading your content. A signed URL includes additional information, for example, an expiration date and time, that gives you more control over access to your content (e.g.
Zapp provides a Video Player Preload Plugin, which can perform request to your signing service prior to playing your content. The protocol follows
pipesv2 endpoints protocol and allows you to leverage context keys.
Setting Zapp Video Player Preload Plugin as a hook to Applicaster Video Player or any other video player will allow you to apply signed url flow on every attempt of users to play video in the app.
In order to use signed URLs, you are expected to have a signing server which could handle HTTP calls and is expected to respond in a JSON:API format.
Pipes2 Signer Endpoint Example
The following is a Pipes2 Signing service Endpoint example implemented with expressjs that returns the expected JSON:API response (shown below):
The response should follow Signed URL JSON schema.
Using Context Parameters
Video Player Preload Plugin can send additional parameters to the Signer Endpoint when instructed to do so. You can read more here. This could be useful in case you would like to get some device or user information in order to sign the stream or return errors for un-permitted users.
Signer Endpoint URL
The Signer Endpoint could be defined in a similar way to Pipes2 Feed Endpoint.
The default Signed URLs service could be set in Video Player Preload Plugin configuration. When using this option, the original stream src url will be added to the
ctx object sent as part of the request.