Gigya Job Openings

accounts.tfa.finalizeTFA REST

Skip to end of metadata
Go to start of metadata

 

 

This method finalizes the two-factor authentication (TFA) flow that started with accounts.tfa.initTFA

The server validates the JWT token, extracts the inner secure ticket and if the flow is:

  • register - the server adds the provider to the "active" providers list of the user, adds the deviceID to the list of verified devices for the user, and reports a 'tfa registration' event.
  • add -  the server adds the provider to the "active" providers list of the user, but does not update the deviceID in the list of verified devices for the user, and reports a 'tfa added' event.
  • verify - the server updates/inserts the deviceID to the list of verified devices for the user, and reports a 'tfa verification' event.
  • edit - the server updates the deviceID in the list of verified devices for the user, and reports a 'tfa edited' event.

 

This method is part of the Customer Identity and the Profile Management - IDS packages. Both packages are premium platforms that require separate activation. If neither are part of your site package, please contact your Gigya Customer Engagement Executive or contact us by filling in a support form on our site. You can also access the support page by clicking "Support" on the upper menu of Gigya's site.

 

Request URL

Where <Data_Center> is:
  • us1.gigya.com - For the US data center.
  • eu1.gigya.com - For the European data center.
  • au1.gigya.com - For the Australian data center.
  • ru1.gigya.com - For the Russian data center.
  • cn1.gigya-api.cn - For the Chinese data center.

If you are not sure of your site's data center, see Finding Your Data Center.

 

Parameters

RequiredNameTypeDescription
gigyaAssertionstringThe JWT token from accounts.tfa.initTFA. It is made up of a header object, a body object and a signature:
Header:

{
  "alg": "http://www.w3.org/2000/09/xmldsig#rsa-sha1",
  "typ": "JWT",
  "x5u": "http://accounts.gigya.com/accounts.tfa.getCertificate"
}

Body:

{
  iss - a string representing the issuer, e.g., "gigya.com". 
  aud - a string representing the TFA provider name, e.g., "gigyaPhone".
  sub - a string representing a unique Gigya identifier for this user.
  action - a string enum representing the requested action type, can be "verify", "edit", or "registerOrVerify".
  params - a JSON object with string properties and values with TFA provider-specific parameters. These are the params from the policy for this provider.
  iat - an integer representing the creation time of this JWT object in UNIX time.
  jti - a string representing the JWT ID; a crypto-strength nonce value.
  ctx - a string representing an encrypted Gigya context.
}

Signature: Computed using the private key matching the public key whose URL is specified in the header.

providerAssertionstringThe JWT token from the TFA provider. The  It is made up of a header object, a body object and a signature:
Header:

{
  "alg": "http://www.w3.org/2000/09/xmldsig#rsa-sha1",
  "typ": "JWT",
  "x5u":
}

Body:

{
  iss - a string representing the issuer, e.g.  "gigya.com". 
  aud - a string representing the TFA provider name, thesame as the issuer of the Gigya assertion that triggered the TFA check, e.g., "gigya.com".
  sub - a string representing the TFA provider's unique identifier for this user. May match Gigya's user identifier from gigya assertion's subject.
  method - a string representing an optional indication of the method used for identifying the user, only relevant to providers who offer multiple methods.
  iat - an integer representing the creation time of this JWT object in UNIX time.
  jti - a string representing the JWT ID; a crypto-strength nonce value.
  rti - a string representing the JTI value of the Gigya assertion that triggered this TFA process. This strongly binds this assertion with the Gigya assertion.
}

Signature: Computed using the private key matching the public key whose URL is specified in the header.

regTokenstringThe regToken returned from the previous API or notifyLogin response.
tempDeviceBooleanIndicates whether this device is temporary and should not be remembered as an active device. The default value is "false". When this value is true the server marks the device as "oneTimeOnly". When login is performed, "oneTimeOnly" devices are treated as not verified.
             
format string Determines the format of the response. The options are:
  • json (default)
  • jsonp - If the format is jsonp then you are required to define a callback method (see parameter below).
callback string This parameter is required only when the format parameter is set to jsonp (see above). In such cases this parameter should define the name of the callback method to be called in the response, along with the jsonp response data.
httpStatusCodes Boolean The default value of this parameter is false, which means that the HTTP status code in Gigya's response is always 200 (OK), even if an error occurs. The error code and message is given within the response data (see below). If this parameter is set to true, the HTTP status code in Gigya's response would reflect an error, if one occurs.

Authorization Parameters

Each REST API request must contain identification and authorization parameters.

Some REST APIs may function without these authorization parameters, however, when that occurs, these calls are treated as client-side calls and all client-side rate limits will apply. In order to not reach client-side IP rate limits that may impact your implementation when using server-to-server REST calls, it is Recommended Best Practice to always sign the request or use a secret. A non-exhaustive list of REST APIs that this may apply to are as follows:

  • accounts.login
  • socialize.login
  • accounts.notifyLogin
  • socialize.notifyLogin
  • accounts.finalizeRegistration
  • accounts.linkAccounts

Please refer to the Authorization Parameters section for details. 

 

Response Data

FieldTypeDescription
 
errorCode integer The result code of the operation. Code '0' indicates success, any other number indicates failure. For a complete list of error codes, see the Error Codes table.
errorMessage string A short textual description of an error, associated with the errorCode, for logging purposes. This field will appear in the response only in case of an error.
errorDetails string This field will appear in the response only in case of an error and will contain the exception info, if available.
fullEventName string The full name of the event that triggered the response. This is an internally used parameter that is not always returned and should not be relied upon by your implementation.
callId string Unique identifier of the transaction, for debugging purposes.
time string The time of the response represented in ISO 8601 format, i.e., yyyy-mm-dd-Thh:MM:ss.SSSZ or
statusCode integer The HTTP response code of the operation. Code '200' indicates success.
This property is deprecated and only returned for backward compatibility.
statusReason string A brief explanation of the status code.
This property is deprecated and only returned for backward compatibility.

 

A field that does not contain data will not appear in the response.

 

Response Example

{
  "statusCode": 200,
  "errorCode": 0,
  "statusReason": "OK",
  "callId": "64803b45bb544bc289fa19f02f3b93b9",
  "time": "2015-03-22T11:42:25.943Z",
  "context": "R250462464"
}

 

Additional Information

When TFA is required during Login, a temp device is saved for 1 minute so that if an account gets a pending registration error it will not need an additional TFA afterwards.