I'm trying to setup two remoting channels to meet security requirement of different services. The code looks like below:

services-config.xml
Code:
<services>
     <default-channels>
           <channel ref="im-amf"/>
        </default-channels>
    </services>

    <security>
        <security-constraint id="authenticatedUser">
            <roles>
                <role>ROLE_USER</role>
            </roles>
        </security-constraint>
         
    </security>

    <channels>
    
        <channel-definition id="im-amf" class="mx.messaging.channels.AMFChannel">
            <endpoint url="http://{server.name}:{server.port}/{context.root}/messagebroker/amf" class="flex.messaging.endpoints.AMFEndpoint"/>
        </channel-definition>
        
        <channel-definition id="enquery-amf" class="mx.messaging.channels.AMFChannel">
            <endpoint url="http://{server.name}:{server.port}/{context.root}/messagebroker/amfenquery" class="flex.messaging.endpoints.AMFEndpoint"/>
        </channel-definition>

  </channels>
spring configuration file
Code:
<flex:message-broker services-config-path="classpath:/flex/services-config.xml">
		<flex:secured>
			<flex:secured-channel channel="im-amf" access="ROLE_USER" />
		</flex:secured>
	</flex:message-broker>
<flex:remoting-destination ref="testRemoting" channels="im-amf" />
The problem is that spring keeps mapping testRmoting service to BOTH channels which creates a huge security hole. I have tried to use flex:remoting-service tag instead of services block in services-config.xml, and still got the same result.

Any one have idea of what I'm doing wrong?