Skip to main content
K
k_wong
Participant
November 4, 2011
Answered

config fms 4.5 for protected On-demand Apple HTTP Live Streaming

  • November 4, 2011
  • 1 reply
  • 1644 views

Hi~

I am trying to config custom encryption key for different pieces of content at streaming level using jit.conf for On-demand Apple HTTP Live Streaming.

I tried to set  "HLSEncryptionScope content" in httpd.conf and placed jit.conf in ../webroot/vod but not success, the m3u8 generate not contains EXT-X-KEY.

Is my jit.conf placed wrongly?

and, I tried and got nothing in access plugin log file while i http stream a m3u8 file, is it possible to log HTTP Live Streaming using plug-in?
can plugin got any event triggered by http streaming?

Would anyone helps,

many thanks.

    This topic has been closed for replies.
    Correct answer NpComplete

    Hi,

    Thanks for using FMS 4.5.

    In case you have configured, HLSEncryptionScope content (and uncommented it ) under <Location /hls-vod> , you may configure the encryption settings under jit.conf. jit.conf has to be placed along with the content file. So in case if your content file is placed under ../webroot/vod .. jit.conf has to be in ../webroot/vod .. In case your content file is inside for example ../webroot/vod/myhlsFile.. jit.conf too needs to be there..

    Now make sure,

    1. In jit.conf you have correctly mentioned the key file path and key uri. Remember both needs to be mentioned in the jit.conf

    2. Make sure jit.conf is a valid xml (To avoid editing errors). Open in any web-browser to validate.

    3. Make sure the key file is generated using scramble tool under \tools\scramble

    4. Initially for test purpose test with a key uri with http protocol. If things run successful, then try with https

    You may check the error logs (inside <Apache>/logs ) for any errors in reading the configurations or applying the configurations.. You may also change the log level to debug in httpd.conf

    Thanks

    1 reply

    N
    Adobe Employee
    NpCompleteCorrect answer
    Adobe Employee
    November 4, 2011

    Hi,

    Thanks for using FMS 4.5.

    In case you have configured, HLSEncryptionScope content (and uncommented it ) under <Location /hls-vod> , you may configure the encryption settings under jit.conf. jit.conf has to be placed along with the content file. So in case if your content file is placed under ../webroot/vod .. jit.conf has to be in ../webroot/vod .. In case your content file is inside for example ../webroot/vod/myhlsFile.. jit.conf too needs to be there..

    Now make sure,

    1. In jit.conf you have correctly mentioned the key file path and key uri. Remember both needs to be mentioned in the jit.conf

    2. Make sure jit.conf is a valid xml (To avoid editing errors). Open in any web-browser to validate.

    3. Make sure the key file is generated using scramble tool under \tools\scramble

    4. Initially for test purpose test with a key uri with http protocol. If things run successful, then try with https

    You may check the error logs (inside <Apache>/logs ) for any errors in reading the configurations or applying the configurations.. You may also change the log level to debug in httpd.conf

    Thanks

    K
    k_wongAuthor
    Participant
    November 4, 2011

    Thank you so much for your fast and helpful reply ^.^

    i figured out that key uri &  key file was wrongly configurated.

    the settings for phls at streaming level is work fine now.

    btw,

    can we able to do something or log any event triggered by http streaming in plugin, so that the auth plugin or access plugin which we implemented previously at fms 3.5 can be reused?

    Thank you so much for your helps. :]

    N
    Adobe Employee
    NpComplete
    Adobe Employee
    November 4, 2011

    HTTP streaming is served by the Apache module. There is no information that goes into the FMS for this except the publishing of livestream for HTTP streaming purpose. So there is no way currently that you can re-use the same. We rely on Apache's framework like access logs and error logs (inside Apache/logs folder) for logging any HTTP related event. Currently, I can suggest you to work with Apache's mod_auth "http://httpd.apache.org/docs/2.0/mod/mod_auth.html" or mod_access "http://httpd.apache.org/docs/2.0/mod/mod_access.html"

    Terms & ConditionsAccessibility statement
    Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices