MachineKey::Protect Method (array<Byte>^, array<String^>^)
Protects the specified data by encrypting or signing it.
Assembly: System.Web (in System.Web.dll)
public: static array<unsigned char>^ Protect( array<unsigned char>^ userData, ... array<String^>^ purposes )
The data to protect. This data is passed as plaintext.
Return ValueType: array<System::Byte>^
The ciphertext data.
This method supersedes the Encode method, which requires the caller to specify whether the plaintext data should be encrypted, signed, or both. The method performs the appropriate operation and securely protects the data. Ciphertext data produced by this method can only be deciphered by the Unprotect method.
The purposes parameter is an optional list of reasons that can lock the ciphertext to a specific purpose. This parameter lets you isolate cryptographic operations performed by different subsystems within an application. A malicious client should not be able to get the result of one subsystem's Unprotect method, which could compromise application security. The purposes parameter helps ensure that protected data can only be used by the component that originally generated it. Applications should make sure that each subsystem uses a unique purposes list.method and feed it as input to another subsystem's
For example, to protect or unprotect an authentication token, you could call the method using code like the following example:
Applications can dynamically generate the purposes parameter. In that case, prefix user-supplied values with a fixed value (like "Username: " + username) to minimize the risk of a malicious client crafting input that matches a token that is used by some other part of the system. Any dynamically-generated strings should come after fixed strings. For example, to protect or unprotect a private message that is tied to a specific user, use code like the following example:
When the Unprotect method is called, the value that is provided for the purposes parameter must be the same value that was provided to the method. Otherwise the operation will fail with a CryptographicException exception.
The configuration settings that are required for the MachineKeyCompatibilityMode::Framework45 option are required for this method even if the MachineKeySection::CompatibilityMode property is not set to the Framework45 option.
Available since 4.5