Configuration Guide

On its own, the Message Security Layer (MSL) Framework does not dictate any specific cryptographic algorithms or schemes to ensure the security and protocol objectives are met. An application must specify the mechanisms by which MSL can meet these objectives. In some cases an application may have to employ custom mechanisms due to platform limitations or to take advantage of unique platform features.

There may be platform or application limitations that prevent an application from being able to meet all of the objectives all of the time. Any known issues are documented below.

An application must configure its MSL stack to support the following operations:

• Local and remote entity authentication.
• User authentication.
• Key exchange.
• Token issuance (if applicable) and protection.

An application must choose the security properties required by each type of message it sends, and enforce the security properties it requires from each type of message it receives.

This guide includes some common client and server configurations.