Installation guide

Authorization adaptors can:
• Authorizeconnectionstotheserver
• Authorizeplayingastreamorseekinginastream
• Authorizepublishingastream
• Disconnectclientsfromtheserver
• Callamethodinserver-sideActionScript
• Delivercontenttoclientsaccordingtotheirgeographiclocation,subscriptionlevel,and
streamOrigin
• Limittimeanddurationofauser’saccesstospecicstreams
• Mapalogicalstreampathtoaphysicalstreampath.Forexample,aclientrequeststhestream
foo.v, but because the client is not a premium member of the service and should only receive
the low-quality version of that content, bar.v is served instead.
Unlike the access adaptor, you can use multiple authorization adaptors to sequentially perform
actions on the incoming event. For example, aut h 1.dll (orauth1.so)couldauthorizethe
client connection; auth 2.d ll(orauth2.so)couldthenauthorizethatclienttopublisha
stream, and so on. e server applies the adaptors in alphabetical order.
As you can see, authorization adaptors can be very powerful for stream security and access
control at a granular level. ey can be congured to implement custom functionality ranging
from rights management to logging.
Dynamic access control
When clients access the server, they have full access to all streams and shared objects by default.
Access control is possible, however, using server-side ActionScript. You can create a dynamic
accesscontrollist(ACL)thatcontrolswhohasaccesstoread,create,orupdatesharedobjects
or streams.
Inserver-sideActionScript,eachclientthatconnectsisassignedtoaClientobject.EachClient
object has readAccess and writeAccess properties. ese properties can accept multiple
comma-delimited values. By setting these values when you accept the client connection, you can
control which streams and shared objects any given client can access.
Stream encryption
FlashMediaServer3.5oerstwooptionsforencryptingyourstreams:SSLandRTMPE.
SSL
Feature available in Flash Media Streaming Server and Flash Media Interactive Server; requires
Flash Player 8 or later.
InearlierversionsofFlashMediaServer,encryptedstreamingwasavailableusingSSLdelivery
through RTMPS. is form of encryption is still supported in Flash Media Server 3.5.
Implementationrequirestheuseofathird-partycerticatewithsomeserver-sideconguration.
Flash Media Server 3.5 now oers an easier, optimized way to implement an encryption solution
usingencryptedRTMP(RTMPE).
RTMPE
Feature in Flash Media Streaming Server and Flash Media Interactive Server; requires Flash Player
9,0,115,0 or later.
EncryptedRTMP(RTMPE)isenabledonFlashMediaServerbydefault.Itallowsyoutosend
streamsoveranencryptedconnectionwithoutrequiringcerticatemanagement.Oering
secure128-bitencryption,RTMPEisonlysupportedinFlashPlayer9orlater,withtheupdated
FLVPlaybackcomponentandNetConnectionclasses.BothSSLandRTMPEcanalsobe
“tunneled”toensureconnectivitythroughnetworkrewalls.RTMPEistherecommendedform
ofencryption,becauseitiseasiertodeployandismuchfasterthanSSL.
55