RTMP streaming... Couple security questions
1)I use Adobe Flash Live Media Encoder to send stream from camcorder to Wowza media server.
But if someone knows rtmp streaming URL he will be able to broadcast on my wowza media server. Is it possible configure authentification on Wowza media server?
I can't restrict access using firewall rules because on laptop where installed FLME always dynamic IP-address
2)On my website installed flowplayer and it connects to Wowza Media Server.
How can i restrict access to Wowza for only my website. For example by domain name like http://lalala.ru/
is it possible?
thx for reply Charlie,
1)Seems rtmpe not supported by Adobe Flash Media Live Encoder...
2)When i add username and password to
C:\Program Files\Wowza Media Systems\Wowza Media Server 2.1.2\conf\publish.password
and restart wowza service. I can broadcast using FLME without password request.
RTMPE is supported by FMLE.
Adding a password to the publish.password file does not enable authentication. You have to download the MediaSecurity package, copy the jar file to Wowza /lib folder, configure the Application.xml with ModuleRTMPAuthenticate (follow the included guide), then restart Wowza.
The credentials you added to /conf/publish.password file will be needed in FMLE when you connect.
rrlanham, thank you for reply.
ok, i will try it!
but when i enter rtmpe://127.0.0.1/live in FMS URL fields
Adobe FMLE shows message
only rtmp[t] format supported.
if i use live, live-record wowza stream types.
and flowplayer to playback streams on website.
what modules and preferences i should use to be protected from re-streaming my live stream to other websites?
Yes, sorry, you're right. I get same complaint from FMLE. You can still use rtmpe when streaming to Flash clients that are subscribing to a stream that is published with rtmp from FMLE.
ok, if i use rtmp can i use authentication?
or it makes no sense because password will be sent in the plain text?
what about my second quetion?
I think authentication is digest mode. The authentication is handled by the encoder independent of the stream, at connection time before a stream is published.