-
1. Re: How to secure live encoding
JayCharles Jan 26, 2010 12:05 PM (in response to CarphuntinGod)You can't restrict what clients can and can't do on a given Vhost by configuration.
I find that the best solution is to secure your application via actionscript. See discussion here:
-
2. Re: How to secure live encoding
CarphuntinGod Jan 26, 2010 2:22 PM (in response to JayCharles)Well, at least for now we've loaded the fmle authentication module into our 352 fmis. Unless you people tell me differently, it appears you have to give a name and pass to get an encoder to talk through our box. this appears to be enough for us to stop the current pirate pumping stuff off our server.
Now that we have this auth module in, where do access FMLE attempts/denies get logged? The access.log files in /fms35server/logs don't appear to show user access granted/denied entries. do they exist somewhere else? or do we have to do some alteration to logger.xml?
-
3. Re: How to secure live encoding
Janaki Lakshmikanthan Jan 29, 2010 1:32 AM (in response to CarphuntinGod)If a user tries to connect to FMS and the server denies the connection, access.log should have events "connect" and "disconnect" logged in it with relevant status code - The reason why it is disconnected. If you are managing this using Authorization PlugIn, you should find similar logs in authEvent log file as well. The status code list and its description can be seen in "FMS Configuration and Admin" doc. Make sure you have enabled required Events and fields for 'access' and 'authEvent' logs in Logger.xml.
Regards,
Janaki L



