Security - Adobe FLEX 2-MIGRATING APPLICATIONS TO FLEX 2 Manual

The following configuration files were renamed since Flex 2 Beta 2:
Flex 1.x Name
flex-enterprise-services.xml, became fds-config.xml
flex-data-service.xml, became fds-data-management.xml, data-management-config.xm
flex-message-service.xml, became fds-messaging.xml,
flex-remoting-service.xml, became fds-remoting.xml,
flex-proxy-service.xml, became fds-proxy.xml,

Security

This section describes changes to Flex security.
Flex changes
You do not define the security of web services and other data services in the flex-config.xml
file. You now define them in the services-config.xml and related files.
ActionScript changes
The following general changes were made to ActionScript:
The System.security.* package is now named Security.*.
■
The
■ Security.allowDomain()
longer open up all SWF files in the caller's domain; instead they now affect only the
calling SWF file itself.
Setting Security.exactSettings no longer affects all SWF files in the caller's domain; instead
■
it now affects only the calling SWF file itself.
The
■ LocalConnection allowDomain()
longer callback methods for authors to define; instead they are now built-in methods for
authors to call, and follow the same semantics as the
Security.allowInsecureDomain()
When you use XMLSocket.connect to contact a server outside a SWF file's own domain,
■
the default policy file location is no longer on an HTTP server in the same domain;
instead it is now an XMLSocket policy file obtained from the same port as the main
connection attempt. You can use the
this default location in the same way you used it in Flex 1.5.
and
Security.allowInsecureDomain()
and
allowInsecureDomain()
Security.allowDomain()
methods.
Security.loadPolicyFile()
Flex 2 Name
services-config.xml
messaging-config.xml
remoting-config.xml
proxy-config.xml
methods no
methods are no
method to override
Security
and
155