getChallenge SOAP Request Structure
- 20 Jan 2025
- 1 Minute à lire
- SombreLumière
- PDF
getChallenge SOAP Request Structure
- Mis à jour le 20 Jan 2025
- 1 Minute à lire
- SombreLumière
- PDF
The content is currently unavailable in French. You are viewing the default English version.
Résumé de l’article
Avez-vous trouvé ce résumé utile ?
Merci pour vos commentaires
A getChallenge SOAP request typically uses the following format:
<soapenv:Envelope
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">
<soapenv:Header/>
<soapenv:Body>
<aut:getChallenge>
<credentialAttributeSet>
<!--Zero or more repetitions:-->
<attributes>
<value xsi:type="xsd:!!!!!!">?????</value>
<attributeID>?????</attributeID>
</attributes>
</credentialAttributeSet>
</aut:getChallenge>
</soapenv:Body>
</soapenv:Envelope>
The SOAP body element should only contain a getChallenge 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 getChallenge request must follow these additional rules:
- The getChallenge element should contain one credentialAttributeSet element.
- The credentialAttributeSet element should contain zero or more credential attributes elements.
Cet article vous a-t-il été utile ?