Inspiring

Answered

httpd.conf level Flash Access for VOD in FMS 4.5.1

Forum|Forum|14 years ago
March 16, 2012
1 reply
1333 views

Hi

I am looking for a way to set up individual Flash Access protection settings for each of some <Location /{url-path}> tags in httpd.conf in the Apache. I have found in the documentation that EncryptionScope can be set to content or server. If I set it to server and use FlashAccessV2 as ProtectionScheme, how or where do I specify the Flash Access certifications and so on?

best regards

Johan Acevedo

This topic has been closed for replies.

Correct answer SE_0208

You can use it as below - i think its miss from our side on documentation front - we will get that corrected and i have filed the bug for same. Thanks for letting us know.

HttpStreamingJITPEnabled true

HttpStreamingContentPath "../webroot/vod"

JitFmsDirPath ".."

EncryptionScope server

ProtectionScheme FlashAccessV2

FlashAccessCommonKeyFile <location to key file to be used>

FlashAccessLicenseServerURL <http://<license-server-url>>

FlashAccessTransportCertFile <location to the certificate files>

FlashAccessLicenseServerCertFile <location to license server certificates>

FlashAccessPackagerCredentialFile <location to packager credential file>

FlashAccessPackagerCredentialPassword <password for packager credentials>

FlashAccessPolicyFile <policy to be used to packaging the content>

Options -Indexes FollowSymLinks

</Location>

S

StreamChimp

Participant

Hi

If you set the scope to server, that tells fms to use http.conf (jithttp_module)

Ive not seen anyone set up individual settings for locations, but I guess you can try the tags that you find in the normal /hds-vod location

J

JohanAcevedoAuthor

Inspiring

I found this documentation for what fields/tags/attributes that are availible for the jithttp_module and nothing there enables me to specify the Flash Access credentials for the entire location/application.

I can solve my problem with the jit.conf file, but I don't want that file to be exposed to an FTP user who upload material to the publish folder.

By default in the FMS now, all jit.conf files are exposed to normal HTTP requests through the Apache unless you yourself put a limitation in the Apache httpd.conf. This might be a overlooked security error in the update from FMS 4.5.0 to 4.5.1 when HTTP (HDS) traffic was changed to go through the Apache only by default.

S

SE_0208Correct answer

Adobe Employee