43
FLASH
MEDIA
SERVER
4.5
CONFIGURATION
AND
ADMINISTRATION
Configuring the server
Last updated 11/28/2012
<VirtualHost>
...
<Proxy>
<SSL>
<SSLClientCtx>
<SSLVerifyCertificate></SSLVerifyCertificate>
<SSLCACertificatePath></SSLCACertificatePath>
<SSLCACertifcateFile></SSLCACertificateFile>
<SSLVerifyDepth></SSLVerifyDepth>
<SSLCipherSuite></SSLCipherSuite>
</SSLClientCtx>
</SSL>
</Proxy>
</VirtualHost>
When the
SSL
tag is present, the entire
SSL
section is used to configure the virtual host. If an
SSL
tag is omitted
from this section, the server uses the default settings.
2
Restart the server.
Configure Flash Media Server to work with a hardware SSL proxy
When you use a hardware SSL proxy, you don't need to configure Flash Media Server for SSL. The hardware sits
between Flash Media Server and the Internet. Data sent between Flash Media Server and the hardware is unencrypted.
The hardware encrypts the data and forwards it to the Internet.
Configure the hardware to listen externally on port 443 to receive encrypted data sent over Internet from clients.
Configure the hardware to forward data to Flash Media Server on port 1935. Flash Media Server listens on port 1935
by default. If you’ve changed the default port, configure the hardware to forward data on that port.
Configure RPCs (Remote Procedure Calls)
Flash Media Server provides settings in the Application.xml file for configuring which RPC methods can be called. The
default is to block all RPC calls.
You can enable RPCs by setting the
<RPC>
element’s
enable
attribute to
true
; for example:
<RPC enable="true">
After enabling RPCs, you must then list individual methods that are allowed. Each type of class—Client,
NetConnection, Stream, and SharedObject—has its own whitelist of methods that can be called. If a method or object
is not explicitly listed in the whitelist, then it is considered blocked.
The settings for RPCs are in the
<Security><RPC>
element of the Application.xml file. This element contains the
following sub-elements:
•
<Client>
— All methods blocked by default.
•
<NetConnection>
— Only the
onStatus()
method is allowed by default, if RPCs are enabled.
•
<SharedObject>
— All methods blocked by default.
•
<Stream>
— Only the
onStatus()
method is allowed by default, if RPCs are enabled.
Each of these sub-elements takes a
<Method>
sub-element. Each
<Method>
sub-element takes an
<Allow>
sub-
element. The
<Allow>
sub-element is a comma-delimited list of allowed methods.
To add a method to a class’s whitelist:
1
Enable RPCs by setting the
<RPC>
element’s
enabled
attribute to
true
; for example: