Did not get clearly when you say business rules - are you saying that some features which work in FMS dont work for HLS ? If that's the case then it migth be expected - HLS is Apache based service - it does not directly interact with FMS except for getting source for streaming.
I thin if you can elaborate giving us one example of what were you expecting to work and is not working - that might help us to answer better.
Yeah, I mean by "business rules" some code we wrote inside our FMS application to verify some attributes from the user who's trying to watch the video and these verifications will allow he to watch or not.
On HLS it seems the user watch without any kind of verification. The user's connection try by HLS does not interact with our FMS application
something similiar i have discussed on this forum, here:
I think you must write an iOS app for all your needs and try to solve this outside FMS - in your apache to be more concrete.
For authentication, we've tested this:
- adding basic user/pass authentication to the location hls-live (in httpd.conf)
- viewing the stream through browser via https://user:pass@name-of-the-server/..../..m3u8
(user/pass sent encrypted via https, you need a certificate on the server to do all this)
That way, only authenticated user will view the stream.
(did it for the hds-live also)
not sure if this will work with iOS app though... my best guess is - it would.
I think that nothing you have server side as a asc script for rtmp will work for http streaming, someone correct me if i'm wrong...
I REALLY hope that some next version will include anything related to HLS protection in this context.
Hi nnmk - thanks for sharing this info - its really helpful. I agree it would nice which is something in build which would help users to authenticate by default. I'll try to take this forward.