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 IndexWebSphere Message Broker SupportSet SOAPRequest node securityProfileName dynamically

Post new topicReply to topic
Set SOAPRequest node securityProfileName dynamically View previous topic :: View next topic
Author Message
leao
PostPosted: Wed Aug 19, 2020 7:03 am Post subject: Set SOAPRequest node securityProfileName dynamically Reply with quote

Newbie

Joined: 06 Dec 2018
Posts: 6

Is there any way to set a SOAP Request node's securityProfileName property dynamically, for example in a Compute node?

Here's the scenario: Depending on the input message of the flow, one of two different security profiles are used. So if input=A, use securityProfileA, if input=B, use securityProfileB.

I thought maybe it would be possible to set this in the local environment, but according to this page https://www.ibm.com/support/knowledgecenter/SSMKHH_9.0.0/com.ibm.etools.mft.doc/ac56192_.htm, this isn't possible.

The solution that I use now is two separate SOAPRequest nodes, where I set each security profile in the BAR override file.

Are there any better solutions?
Back to top
View user's profile Send private message
Vitor
PostPosted: Wed Aug 19, 2020 7:28 am Post subject: Re: Set SOAPRequest node securityProfileName dynamically Reply with quote

Grand High Poobah

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

leao wrote:
Are there any better solutions?


I don't know about "better", but one option would be have a single SOAPInput node that doesn't authenticate, then a Filter node (or similar) that routes the message to one of two SecurityPEP nodes based on the criteria. One node uses profile A, the other profile B, and both route back to the downstream processing.

Easier to deploy, fewer moving parts and a single input node. This meets the standard for "better" in most states.

Other, even better solutions are undoubtedly possible and someone will be along in a minute to suggest one.
_________________
Honesty is the best policy.
Insanity is the best defence.
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 IndexWebSphere Message Broker SupportSet SOAPRequest node securityProfileName dynamically
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.