string Base64 encoded RSA encrypted JSON string. This data is the user response
directly from their device. It is encrypted on the device. As such, the LaunchKey Platform API has no knowledge of the
contents of the encrypted data. Once Base64 decoded, decrypt the result with the private key of
the RSA public/private key pair associated with the service whose Service Key was included in the
request. The resulting JSON will have the following attributes:
|response:||boolean The users response to the authorization request.
true if approved and
|auth_request:||string Request-specific string used to match auth_request value returned from corresponding
|device_id:||string Unique identifier for the device the user used to respond to the Auth Request
|app_pins:||string A list of up to 5 codes separated with commas. The list is intended for for device validation
in conjunction with a
device_id. Devices will rotate out app pins as a queue, first in - first out (FIFO).
As such, they are rotating shared secrets known only to the device and the service. App pins can be used to
protect against a myriad of potential attacks. However, they do run the risk of devices getting "out of sync"
and resulting in devices not being able to authenticate. If you implement auth pins in your solutions, you
will need to build in a recovery mechanism to reset the known app pins and re-sync the device.