--- title: "Signature Validation Using Secure Channel" slug: "oas-fullsdk-pg-signature-validation-using-secure-channel-3-28" updated: 2025-07-07T15:34:16Z published: 2025-07-07T15:34:16Z canonical: "docs.onespan.com/oas-fullsdk-pg-signature-validation-using-secure-channel-3-28" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.onespan.com/llms.txt > Use this file to discover all available pages before exploring further. # Signature Validation Using Secure Channel To perform signature validation using Secure Channel, the following two operations must be executed in this order: 1. Get signing request (see [Get signing request](/sec/docs/oas-fullsdk-pg-get-signing-request-3-28)) 2. Secure channel message signature validation (see [Secure Channel message signature validation](/sec/docs/oas-fullsdk-pg-secure-channel-message-signature-validation-3-28)) For this operation to succeed, the following administrative tasks should be performed in OneSpan Authentication Server: To configure OneSpan Authentication Server for the get signing request operations 1. Use the pre-defined IDENTIKEY Signature Validation with Secure Channel policy or define a policy that inherits from that policy. 2. Register a client component and assign the policy to it. 3. Import authenticators that are compliant with multi-device licensing (MDL) and support Secure Channel. 4. Create users, assign authenticator licenses to them, and activate a new authenticator instance for their devices.