--- title: "getSecureChallenge SOAP Request Structure" slug: "oas-fullsdk-pg-getsecurechallenge-soap-request-structure-3-29" updated: 2026-01-12T11:31:46Z published: 2026-01-14T17:17:26Z canonical: "docs.onespan.com/oas-fullsdk-pg-getsecurechallenge-soap-request-structure-3-29" --- > ## 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. # getSecureChallenge SOAP Request Structure A getSecureChallenge SOAP request typically uses the following format: ```markup 0 CREDFLD_PASSWORD_FORMAT user1 CREDFLD_USERID VDS0000001-1 CREDFLD_SERIAL_NO test message CREDFLD_CHALLENGE_MESSAGE Authentication with Secure Channel Sample Client CREDFLD_COMPONENT_TYPE ``` The SOAP body element must only contain a single getSecureChallenge element (line 8). This element is defined in the namespace aut. Therefore, the aut namespace needs to be declared in the Envelope element as an attribute. A valid getSecureChallenge request must follow these additional rules: - The getSecureChallenge element must contain one attributeSet. - The attributeSet element must contain the minimum number of required attribute elements. - Either a CREDFLD_REQUEST_BODY element or a CREDFLD_CHALLENGE_MESSAGE element with an optional CREDFLD_TRANSACTION_TITLE element must exist.