That's why we don't expose admin service requests to the public. Do it from the server side.

I think the OP was wondering about exposing the username and password on the client side. If the question was actually about man-in-the-middle attacks sniffing out the credentials when making a server to server request, please correct me.

Regardless of the method being used to make the request of the admin service, never expose the admin service credentials to a client side application, unless that application is only accessible to authorized users who should have access to the FMS admin service. If you provide those credentials (via hard code or via service request) to a client side application that is accessible to the public or otherwise unauthorized admin service users, you immediately compromise your server security.

That's what i thought you meant.

The answer here is, don't do it. If you need to have data from the admin service provided to your client side application, use a server side application (php, asp, .net, etc) to make the request of the FMS admin service, and then pass only the required data to the client side application. That way, you just need to store your FMS admin credentials on the server side, and  you don't expose them elsewhere.

Alternately, you can connect to the admin service via your FMS application, and then send the required data to the client through the FMs application.

Sure... you can do that. you can use cURL or httprequest on the php side to pull down the data from the FMS admin service, then parse the XML and return the data to the .swf

That said, if the .swf that needs to consume the data is already connected to an FMS application, it may be more efficient to open a connection from the fms application to the admin service, and then have the FMS application send the required data to the .swf over the existing netconnection. That way, you don't need to have the client side app call out to PHP, and the response data will already be native actionscript objects (so you wouldn't have to write code to parse the response data). In this case, you're using the FMS application as a proxy between the client and the admin service.

In that case, you'd want to go the PHP route, since the client is not a .swf already connected to an FMS app.

Can you post the code you're using? It's impossible to help troubleshoot without knowing what you're trying to do.

It would also be helpful to understand the architecture of your deployment. What is your PHP environment? Is your HTTP/PHP server running on the same server as FMS? Provide as much information as possible.

I tried to access http://flashvisions.com/fms.php, but it just times out with no response. It's impossible to know what's happening if the php program doesn't output anything and you don't post your code.