sorry, there is currently nothing like that in the code base.
Could you explain your use case and what you'd like to see?
Well, the structure is the following:
- A directory listened for incoming data
- A CBR to route data
- Services to process data
We have to make direct remote service invokations (with the service invoker) possible but with at least access control. The FS gateway is not considered as a security hole because the directory is under OS access control.
It doesn't seem to be a blocking issue because we can imagine to place an action before the CBR in witch the message is added a security context. If the gateway had the ability to be set for principal/credentials to add in the message we would use this way.
If the gateway had the ability to be set for principal/credentials to add in the message we would use this way.
You can do this by specifying your own custom org.jboss.soa.esb.listener.message.MessageComposer.
In your jboss-esb.xml you can specify that your MessageComposer should be used like this:
<fs-listener name="FileGateway" busidref="xxxFileMessageBus" is-gateway="true" > <property name="composer-class" value="your.package.YourComposerImpl"/>For an example of a MessageComposer you can take a look at org.jboss.soa.esb.listeners.gateway.LocalFileMessageComposer. It simply adds information about the file being read as properties on the ESB Message object instance.In your case I think what you want is to be able to specify the credentials in the config as properties. This is possible, as you probably can see the MessageComposer interface method setConfiguration gets passed a ConfigTree instance which will contain the properties.For example, if you want to have a username in you config like this:
<property name="username" value="Smith"/>Then you can access that property like this:
config.getAttribute("username");Hope this makes sense.Regards,/Daniel
Of course it makes sense!
Thanks for your help, it solves the issue by a smart way!