Posted: Thu Mar 13, 2014 12:13 pm Post subject: Another WS-Security Consumer Question
Acolyte
Joined: 03 Jun 2008 Posts: 71
I've been reading through the multiple threads here about methods for adding a username/password onto a SOAPRequest but have yet to get a satisfactory direction. Here is our scenario,
We are creating a proxy to a third party webservice. Said proxy will implement WS-Security on the input (SOAPInput) using our internal active directory system. Then, the message flow will apply a different username and password before calling the third party. We chose this approach for two reasons: so that we can manage all internal clients while preventing the third party for generating multiple uses for a single organization; and, so that the global credentials need not be stored in multiple systems.
I have no problem using a UDP and storing the credentials in a properties file from a technical perspective. In fact, that is how we have been handling this scenario for some time. (I do think this approach is pretty deficient from a security perspective) However, I have read the these values can essentially be looked up from a security profile. So far, all of the articles I've read assume the Identity will be passed in via the input and propagated. Because the broker and third party will be authorizing/authenticating these users separately, I cannot just propagate the input credentials. All of this brings me to my question...
Other than a database or UDP (both of which we use), is there a way for the broker platform to store those values and assign them to the outbound SOAP request?
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