ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum IndexGeneral IBM MQ SupportUsing Cluster Workload Exit for security enforcement

Post new topicReply to topic
Using Cluster Workload Exit for security enforcement View previous topic :: View next topic
Author Message
lamtbs
PostPosted: Thu Apr 18, 2019 1:45 am Post subject: Using Cluster Workload Exit for security enforcement Reply with quote

Acolyte

Joined: 07 Nov 2005
Posts: 55
Location: Hong Kong

Customer is a central exchange, connecting to multiple parties. In order for failover to be simplier, they want to use QM Cluster, i.e. us forming P1-cluster with partner-1 talking over P1.xxx.Q, P2-cluster with partner-2 talking over P2.xxx.Q

With standard naming convention, it is easy to guess the cluster name and queue name for partner-3, then I could be faking partner-3's queue and get messages that is intended for partner-3. (assume I am the bad partner-1)

From documentation, seems it is possible to use Cluster Workload Exit to impose some restriction, e.g. if channel is called P1-channel, then only allow message target to P1.xxx.Q. Forbid any messages target for P2 or P3.xxx.Q

Is Workload exit the way to go for such security implementation? Is there further details on how this can be implemented?

Thanks!
Back to top
View user's profile Send private message Send e-mail MSN Messenger
Vitor
PostPosted: Thu Apr 18, 2019 4:55 am Post subject: Re: Using Cluster Workload Exit for security enforcement Reply with quote

Grand High Poobah

Joined: 11 Nov 2005
Posts: 25858
Location: Texas, USA

lamtbs wrote:
Is Workload exit the way to go for such security implementation?


Not even slightly.

There are specific mechanisms and practices for this, outlined in the documentation as Security for queue manager clusters and keeping clusters secure. These describe not only preventing unauthorized queue managers sending or receiving messages but how to stop unauthorized queue managers joining the cluster in the first place.
_________________
Honesty is the best policy.
Insanity is the best defence.
Back to top
View user's profile Send private message
gbaddeley
PostPosted: Mon Apr 22, 2019 4:10 pm Post subject: Reply with quote

Jedi

Joined: 25 Mar 2003
Posts: 2040
Location: Melbourne, Australia

QM Clusters feature is not recommended for B2B MQ messaging interfaces with external partners. It is non-trivial to implement rigorous security controls for authorization (including administrative access and ability for other qmgrs to join the cluster), and communication issues can be more difficult to resolve.
_________________
Glenn
Back to top
View user's profile Send private message
Display posts from previous:
Post new topicReply to topic Page 1 of 1

MQSeries.net Forum IndexGeneral IBM MQ SupportUsing Cluster Workload Exit for security enforcement
Jump to:



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP


Theme by Dustin Baccetti
Powered by phpBB 2001, 2002 phpBB Group

Copyright MQSeries.net. All rights reserved.