The following request body is sent during the deregister call:
<?xml version="1.0" ?>
<S:Envelope
xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Body>
<ns2:deregister
xmlns:ns2="http://soap.skfs.strongauth.com/">
<svcinfo>
{
"did":1,
"protocol":"FIDO2_0",
"authtype":"PASSWORD",
"svcusername":"svcfidouser",
"svcpassword":"Abcd1234!"
}
</svcinfo>
<payload>
{
"keyid":"1-1-testuser1-286",
"appTXID": "exampleappTXID"
}
</payload>
</ns2:deregister>
</S:Body>
</S:Envelope>
Value |
Explanation |
did |
Unique identifier for a cryptographic domain in SKFS. Unless using a StrongKey Tellaro appliance, this defaults to 1. |
protocol |
The FIDO protocol to be used in this request (FIDO2_0). |
authtype |
The type of authentication supplied in this service request—it must be PASSWORD or HMAC (see API Security for details); the example shown here is for PASSWORD type of authentication. |
svcusername |
The username of the service credential requesting this web service. |
svcpassword |
The password of the service credential requesting this web service. When PASSWORD authtype is used, SKFS uses entries in a previously configured Lightweight Directory Access Protocol (LDAP) or Active Directory (AD) to authenticate the credential (see Manage Credentials under [ SKFS ⇒ Administration ⇒ Security ] for details). |
Value |
Explanation |
keyid |
A string identifying the unique FIDO credential within the SKFS. However, the current format is DEPRECATED.
|
appTXID |
An optional string within any SKFS web service request body's payload JSON object that, if added, will attach the appTXID value to the TXID logged by the server. |