<keyAlgorithm> Element for <securityTokenManager>
Specifies the cryptographic algorithm used by the specified XML-based security token to transform data.
<microsoft.web.services3> Element
<security> Element
<securityTokenManager> Element
<add> Element for <securityTokenManager>
<keyAlgorithm name />
Attributes and Elements
Attributes
Attribute | Description |
---|---|
name |
Required attribute. When the security token uses symmetric keys, the name attribute must be one of the following key algorithms: AES128, AES192, AES256, TripleDES. When the security token uses asymmetric keys, the name attribute must be either RSA15 or RSAOAEP, which refer to the RSA15 and RSA_OAEP cryptographic algorithms, respectively. |
Child Elements
None.
Parent Elements
Element | Description |
---|---|
Adds a user-supplied custom security token manager for an XML-based security token to the application domain. |
Remarks
Use the <keyAlgorithm> element to interoperate with other operating systems that use different cryptographic algorithms than WSE does for a specific security token. When you change the defaults, the sender and receiver must be configured to process keys generated for that security token type using the same key generation algorithm.
Example
The following code example specifies that symmetric session keys are generated using the AES192 algorithm for UsernameToken security tokens.
<configuration>
<microsoft.web.services3>
<security>
<securityTokenManager>
<add
type="Microsoft.Web.Services3.Security.Tokens.UsernameTokenManager, Microsoft.Web.Services3, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" priority="1" group="0"
namespace="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
localName="UsernameToken">
<keyAlgorithm name="AES192"/>
</add>
</securityTokenManager>
</security>
</microsoft.web.services3>
</configuration>