MQSeries.net :: View topic - Route-To-Label and Security issue

KSkelton · Posted: Tue Apr 20, 2004 10:17 am Post subject:

Wanted to run this by the group.

I have a Route-To-Label flow which has one input Node.
Many remote client queues point to this Local queue on Integrator.
We have done this to reduce the number of message flows for our client applications. We have an issue now where the security granted on some of these remote queues are more restrictive.

This has created a security hole, since a savvy user could create an XML message for one of the secure queues but place the message on an insecure queue (thus bypassing security) and the message will be routed via the message flow.

I see two ways around this.

1) Split the message flow into two flows. One for secure transactions and one for insecure. (This is fine as long as there are only two levels of security. This can get ugly if there are multiple levels.)

2) Run all the insecure remote queues through a Verification Message flow first. This flow would have a filter which would read the LABEL in the message and compare it against a hard-coded list of insecure labels. If the label is not in the group I toss the message and send an alert.
This would prevent a secure message from being placed on an insecure queue.
This would require maintaing a list of labels.

3) Ok, three solutions. Don't use Route-To-Label for this purpose.

Is there an easier way to do this?
Nothing seems to work at the queue level since the MQMD can be changed by the client program.