| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Consume a Non-Open Standard (Microsoft) Web Service |
« View previous topic :: View next topic » |
| Author |
Message
|
| digoshc |
 Posted: Tue Nov 05, 2013 8:37 am Post subject: Consume a Non-Open Standard (Microsoft) Web Service |
 |
|
Apprentice
Joined: 11 Jul 2013
Posts: 25
|
Hi,
I need to consume a Web Service that uses a extension of WS-Trust created by Microsoft, the SSLContextToken. I don't find any reference on Information Center that explain how to configure a Policy Set for a SSLContextToken assertion and I don't believe that it exists because it seems to be an extension implemented only by Microsoft. Ideally, the Web Service provider should be using only open standards (w3c), but that might not be possible to change. So, I'm posting here to see if you guys already have this situation and which solutions did you considered and implemented. Any thoughts?
Here it's the Contract:
| Code: |
<sp:SymmetricBinding>
<wsp:Policy>
<sp:ProtectionToken>
<wsp:Policy>
<mssp:SslContextToken sp:IncludeToken="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient" xmlns:mssp="http://schemas.microsoft.com/ws/2005/07/securitypolicy">
<wsp:Policy>
<sp:RequireDerivedKeys/>
</wsp:Policy>
</mssp:SslContextToken>
</wsp:Policy>
</sp:ProtectionToken>
<sp:AlgorithmSuite>
<wsp:Policy>
<sp:Basic256/>
</wsp:Policy>
</sp:AlgorithmSuite>
<sp:Layout>
<wsp:Policy>
<sp:Strict/>
</wsp:Policy>
</sp:Layout>
<sp:IncludeTimestamp/>
<sp:EncryptSignature/>
<sp:OnlySignEntireHeadersAndBody/>
</wsp:Policy>
</sp:SymmetricBinding>
|
My Environment is Windows 2008 Server and WMB 8.0.0.2
Thanks in advance,
Rodrigo
Last edited by digoshc on Tue Nov 05, 2013 9:32 am; edited 1 time in total |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Tue Nov 05, 2013 8:40 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| Put an IIS web server in front of broker, and have it resolve the WS-Security and either remove it or renormalize it to w3 standard, and then secure the channel between Broker and the IIS Server. |
|
| Back to top |
|
|
| mgk |
| Posted: Tue Nov 05, 2013 10:40 am Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
Actually, as you are on Windows the easiest way is to use the .NETCompute node to host the WCF Client for the service. Then you can use any supported Microsoft standards for the call. Hosting the WCF Client is really simple and performs very well.
Kind regards.
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Tue Nov 05, 2013 10:46 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| mgk wrote: |
Actually, as you are on Windows the easiest way is to use the .NETCompute node to host the WCF Client for the service. Then you can use any supported Microsoft standards for the call. Hosting the WCF Client is really simple and performs very well.
Kind regards. |
I missed the word "consume". Yes, use .NETCompute for this instead. |
|
| Back to top |
|
|
| digoshc |
| Posted: Tue Nov 05, 2013 12:31 pm Post subject: |
|
|
Apprentice
Joined: 11 Jul 2013
Posts: 25
|
ah, now it makes sense to me! I was doing some research of how IIS would make a WS-Security transformation considering it's not a responsibility of a Web Server. So, I'm going to consider the .NETCompute Node as a WCF client, but I'm now thinking if there is a cross-platform solution to avoid problems if we migrate to AIX in the future.
Thank you guys, I appreciated your prompt reply. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
