Notify me!
-
Recent Posts
Archives
Categories
Stack Exchange MQ Q&A- IBM MQ web api - retrieve messages without message format – stackoverflow.com
- MQCONNX ended with reason code 2393 when connecting mTLS enabled queue – stackoverflow.com
- how to rectify javax.jms.JMSException: Failed to create connection? – stackoverflow.com
- IBM MQ 2059 (MQRC_Q_MGR_NOT_AVAILABLE) error in .NET 9.0 console app using IBMMQClient with certificate-based SSL setup – stackoverflow.com
- TIBCO BWCE Send Message Did Not Send ApplIdentityData MQMD to MQ – stackoverflow.com
Meta
Follow me on Twitter
My Tweets
Category Archives: IBMMQ
Cluster security
Well, the residency to write the new WebSphere MQ Security book is past the halfway point and we are working diligently to finish up on time. I’m happy to say that one of my favorite new security topics is covered … Continue reading
Posted in Events, IBMMQ, News, Publications, WMQ Security
Tagged Admin, Best Practices, clustering, Events, IBM, News, Redbooks, security, WebSphere MQ, WMQ, WMQ Security
1 Comment
New MO71 Beta
Paul Clarke has been working on MO71, a.k.a. mqmon, and has released a beta version of the program. He mentioned that some people have problems getting attachments in email so I offered to host a download. Whether you are a … Continue reading
Thoughts on certificate sharing
The topic of certificate sharing keeps popping up as of late so I wanted to address it here. The main objection to certificate-based crypto seems to be the administrative overhead. After having scripted up certificate management for several customers, I … Continue reading
Posted in IBMMQ, MQ AMS, WMQ Security
Tagged Admin, authentication, Best Practices, certificates, non-repudiation, pki, revocation, security, sharing, tklm, venafi, x.509
Leave a comment
No such thing as a persistent queue!
The widespread usage of the phrase “persistent queue” has a negative impact because people believe that queue attribute actually does something. It’s always worth taking time to stamp out usage of that phrase wherever we find it and I’ll attempt … Continue reading
Posted in IBMMQ
Tagged Admin, antipatterns, Best Practices, commentary, culture, Recommended Practices, WebSphere MQ
5 Comments
PCI zone and non PCI zone in same DataPower box
I’ve been having PCI Déjà vu lately. It seems the same questions keep coming up over and over. One strategy for compliance that is nearly ubiquitous is to segregate the PCI data from the rest of the network. In practical terms, … Continue reading
Posted in General, WMQ Security
Tagged Best Practices, commentary, compliance, PCI, PCI-DSS, Recommended Practices, security
4 Comments
GWC Webinar posted
The WebSphere MQ Security Deeper Dive slides from the Global WebSphere Community webinar last month are now posted on this site. You can get them from the Links page or just click here. If you want the screencast and recording … Continue reading
Posted in IBMMQ, MQ AMS, News, Publications, WMQ Security
Leave a comment
Previous security lab reposted
I acted a bit too hastily in removing the old WMQ Security Lab download when the new one was posted. Several readers reminded me that the new lab is for v7.1 and that isn’t even out yet! Everyone who needs … Continue reading
Posted in IBMMQ, Publications, WMQ Security
Leave a comment
Encrypting passwords in config files – secure or not?
Not long ago a colleague told me he wished that he could use a .kdb format keystore for his Java applications. When I inquired as to why, he said he liked that the .kdb includes the ability to stash an … Continue reading
Posted in General, WMQ Security
3 Comments
WMQ Security in v7.1
For those of you who missed it, Morag presented the WMQ Security session at this year’s WebSphere Technical Conference last week. This was exciting for a few reasons, not the least of which was – did I mention MORAG presented? … Continue reading
Posted in IBMMQ, News, WMQ Security
1 Comment
Sure, its always an MQ problem. Why is that a bad thing?
One recurring theme in the MQ community is that all problems are MQ problems. Never mind that they almost always turn out to be application, network, firewall, SAN, account maintenance, resource constraints, human error or even sabotage, it’s an MQ … Continue reading →
Share this: