Results 1 to 4 of 4

Thread: Common method for client authentication with live MPEG-DASH

  1. #1

    Default Common method for client authentication with live MPEG-DASH


    Please advise if there is a common way to do client authentication when live streaming MPEG-DASH.

    With RTMP, this was rather straight forward; Override as described here,
    ...and check that the requested URL contains a valid token string.

    Eventually, I am aiming to replace an existing system with H.264+RTMP to use HEVC+MPEG-DASH instead, stream to a remote Android box with Kodi.
    The stream not need to be encrypted, but client authentication on connecting is mandatory.

    Please also advise if there is a transport besides MPEG-DASH thought to be suitable for such application.

    Thank you.

  2. #2


    Hi David,

    With regards to token-based security, have you considered Wowza's built-in Secure Token? This can work well with MPEG-DASH streams and a suitable player.


  3. #3


    Thank you Paul,

    Unfortunately, for my application all clients cannot share the same token. (Please correct me if that is indeed possible with "Secure Token")

    There are 10s of clients connecting from random remote locations, each with a unique token which also allows the server to log activity.
    A mechanism to disable individual clients by updating their token stored on server side without affecting others is necessary.

  4. #4



    Secure token does let you define custom parameters as part of the hash which may help you with regards to unique hashes per client? See the section on query parameters.


Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts