--- title: "User Authentication: getChallenge Operation" slug: "oas-fullsdk-pg-user-authentication-getchallenge-operation-3-29" updated: 2026-01-14T12:49:11Z published: 2026-01-14T17:10:07Z canonical: "docs.onespan.com/oas-fullsdk-pg-user-authentication-getchallenge-operation-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. # User Authentication: getChallenge Operation The getChallenge operation sends a requests to OneSpan Authentication Server to generate a server challenge. The returned challenge could then be used for a one-step Challenge/Response user authentication. Two types of server challenges can be generated with the getChallenge operation: 1. General server challenge. A server challenge not tied to a specific user. 2. User-specific server challenge. For this operation to succeed, the following administrative tasks should be performed in OneSpan Authentication Server: To configure OneSpan Authentication Server for getChallenge operations 1. Define an authentication policy that supports the generation of a 1-step server-based challenge. 2. Register a client application, assigning the newly defined authentication policy. 3. Import authenticators supporting Challenge/Response (CR) user authentication. 4. Define users and assign the authenticators. To execute a getChallenge operation, the registered client application should send a getChallenge SOAP command to OneSpan Authentication Server (see [getChallenge SOAP request structure](/sec/docs/oas-fullsdk-pg-getchallenge-soap-request-structure-3-29)). In order for OneSpan Authentication Server to generate a server challenge, the getChallenge command should specify the CREDFLD_COMPONENT_TYPE credential attribute. This credential field attribute indicates the client application type. For user-specific server challenges, the getChallenge command should specify the CREDFLD_COMPONENT_TYPE and CREDFLD_USERID credential attributes. The latter is the user ID for which a server challenge should be generated. > A client application with component type SOAP Auth Client will typically send the following SOAP command to request a challenge for user test1: > > ```markup > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" > xmlns:xsd="http://www.w3.org/2001/XMLSchema" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xmlns:aut="http://www.vasco.com/IdentikeyServer/IdentikeyTypes/Authentication"> > > > > > > > SOAP Auth Client > CREDFLD_COMPONENT_TYPE > > > test1 > CREDFLD_USERID > > > > > > ``` > > This would generate the following getChallenge SOAP response: > > ```markup > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" > xmlns:xsd="http://www.w3.org/2001/XMLSchema" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xmlns:aut="http://www.vasco.com/IdentikeyServer/IdentikeyTypes/Authentication"> > > > > > > RET_SUCCESS > STAT_SUCCESS > 0 > 0 > > > > 32792 > CREDFLD_CHALLENGE > > > 862532550 > CREDFLD_CHALLENGE_KEY > > > > > > > > ``` In this example, the result attribute CREDFLD_CHALLENGE_KEY specifies the challenge identifier used by OneSpan Authentication Server. A Challenge/Response authentication operation for this challenge should add this attribute to its authentication request.