| Author |
Message
|
| duffMan |
 Posted: Mon Mar 24, 2014 1:20 pm Post subject: Basic Authentication credentials |
 |
|
Voyager
Joined: 03 Jun 2002
Posts: 75
|
I have a message flow needs that needs to call a web service using REST, and they require that Basic Authentication be used, with the credentials carried in the HTTP(s) header.
There will be no credentials available on the incoming payload (from EmailInput) into Message Broker to propagate downstream so I must provision the credentials from within the flow itself, either through hardcoded esql, a properties file, or something I haven't considered.
Is there simple method of storing those credentials encrypted via a configurable service or something similar?
Currently on WMB 7.0.0.6.
Thanks. |
|
| Back to top |
|
 |
| martinb |
| Posted: Tue Mar 25, 2014 1:39 am Post subject: |
|
|
Master
Joined: 09 Nov 2006
Posts: 210
Location: UK
|
This is available by configuring your output/request node with a security profile specifying
propagation - TRUE
idToPropagateToTransport - STATIC ID
transportPropagationConfig - <id to match username and password set via mqsisetdbparms>
The WMB v8 and IIB v9 info centers document this in a topic "Configuring SOAPRequest node security" which is somewhat miss leading as you can use this approach on HTTPRequest nodes as well. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Mar 25, 2014 4:37 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| martinb wrote: |
| The WMB v8 and IIB v9 info centers document this in a topic "Configuring SOAPRequest node security" which is somewhat miss leading as you can use this approach on HTTPRequest nodes as well. |
The OP is on WMBv7.0.0.6, which is too early for this function.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| ganesh |
| Posted: Tue Mar 25, 2014 11:17 am Post subject: |
|
|
Master
Joined: 18 Jul 2010
Posts: 294
|
1. Assign a unique label to each of the user name, password combination(Encrypted/plain as you prefer).
2. Store it in the file system.
3. Retrieve the username, password from your flow based on the label. |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Mar 25, 2014 11:55 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ganesh wrote: |
1. Assign a unique label to each of the user name, password combination(Encrypted/plain as you prefer).
2. Store it in the file system.
3. Retrieve the username, password from your flow based on the label. |
Now that's a nice design.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| duffMan |
| Posted: Tue Mar 25, 2014 12:05 pm Post subject: |
|
|
Voyager
Joined: 03 Jun 2002
Posts: 75
|
Well, we do exactly that already for a bunch of flows since before the mqsisetdbparm days, however without the encryption.
I guess what it's looking like now, sans an upgrade is looking for a simple way to encrypt/decrypt. |
|
| Back to top |
|
|
| ganesh |
| Posted: Tue Mar 25, 2014 12:14 pm Post subject: |
|
|
Master
Joined: 18 Jul 2010
Posts: 294
|
| Quote: |
| Now that's a nice design. |
Its your design  |
|
| Back to top |
|
|
| Vitor |
| Posted: Tue Mar 25, 2014 1:04 pm Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| ganesh wrote: |
| Quote: |
| Now that's a nice design. |
Its your design |
I never said I was modest 
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
|
|
