Difference between revisions of "ConfirmRegisterTrustedDeviceChallenge"
Jump to navigation
Jump to search
| Line 2: | Line 2: | ||
Description=Confirm the registration trusted device by challenge code. | Description=Confirm the registration trusted device by challenge code. | ||
| − | After using a method [[ | + | After using a method [[RegisterTrustedDeviceChallange]] in the RegistrationService, the UNIAPI returns a ChallangeCode that should be used to confirm this registration. Once this is done, the device were allowed to access the platform and log gin. |
Revision as of 19:41, 18 September 2014
Description
Confirm the registration trusted device by challenge code.
After using a method RegisterTrustedDeviceChallange in the RegistrationService, the UNIAPI returns a ChallangeCode that should be used to confirm this registration. Once this is done, the device were allowed to access the platform and log gin.
This is used for confirm the registration when we has a device and is necessary to confirme in a web client.
When you want to to confirm the registration device for a non authentication service it should be ...
Parameters
- token (String, required)
- A valid token for identifying the API session context. The token can be anonymous or logged.
- challenge (String, required)
- The challenge code created to register the Trusted Device.
- friendlyName (String, required)
- A friendly name that easily identify the device in the user available devices.
Returns
Returns a JSON object containing true for success.
Example:
{
- "StatusCode": 0,
- "Severity": 1,
- "StatusMessage": "OK",
- "Content": "true"
}
Exceptions
Caching
This method is not cached.
Known issues
- None
Version history
| API Version Number | Change description | Changes author |
|---|---|---|
| 1.0 | Initial method design | Harley Cabral |
