Related to my previous blog on WS-Security interop with WebSphere.
Recommended combination of the crypto algorithms is AES256 for symmetric encryption and RSA-OAEP for key-wrap. In Indigo for example, this is the default Algorithm suite used. WSE2.0 used RSA1.5 + AES128 by default, which will most likely change in WSE3.0.
However, there isn't a great deal of commonality yet in what defaults different WS-Security toolkits use. Here is how to configure WSE to use other encryption and key-wrap algorithms.
For example, to make WSE to use TripleDes for encryption and/or RSA-OAEP for key transfer, add the following in config:
<microsoft.web.services2>
...
<security>
....
<binarySecurityTokenManager
valueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3">
<sessionKeyAlgorithm name="TripleDES"/> <!-- add this to switch to TripleDes from default AES128 -->
<keyAlgorithm name="RSAOAEP"/> <!-- add this to switch to RSA-OEAP from default RSA15 -->
</binarySecurityTokenManager>
</security>
...
<microsoft.web.services2>
or in code:
ISecurityTokenManager stm = SecurityTokenManager.GetSecurityTokenManagerByTokenType(WSTrust.TokenTypes.X509v3);
stm.DefaultSessionKeyAlgorithm = "TripleDES";
stm.DefaultKeyAlgorithm = "RSAOAEP";
Posted
Apr 14 2005, 01:02 AM
by
kirill-gavrylyuk