Difference between revisions of "Updox HMAC Authentication2"
From Updox API
| Line 9: | Line 9: | ||
} | } | ||
the HMAC to-be-hashed message is defined as: [vendorId]:[vendorPassword]:[updox-timestamp] | the HMAC to-be-hashed message is defined as: [vendorId]:[vendorPassword]:[updox-timestamp] | ||
| + | |||
| Line 19: | Line 20: | ||
} | } | ||
} | } | ||
| + | |||
| + | |||
| + | |||
the HMAC to-be-hashed message is defined as: [vendorId]:[vendorPassword]:[accountId]:[updox-timestamp] | the HMAC to-be-hashed message is defined as: [vendorId]:[vendorPassword]:[accountId]:[updox-timestamp] | ||
Revision as of 17:30, 17 January 2014
For
{
"auth": {
"applicationId": "updox",
"applicationPassword": "password",
"accountId": "",
"userId": ""
}
}
the HMAC to-be-hashed message is defined as: [vendorId]:[vendorPassword]:[updox-timestamp]
{
"auth": {
"applicationId": "updox",
"applicationPassword": "password",
"accountId": "100",
"userId": ""
}
}
the HMAC to-be-hashed message is defined as: [vendorId]:[vendorPassword]:[accountId]:[updox-timestamp]
{
"auth": {
"applicationId": "updox",
"applicationPassword": "password",
"accountId": "100",
"userId": "100"
}
}
the HMAC to-be-hashed message is defined as: [vendorId]:[vendorPassword]:[accountId]:[userId]:[updox-timestamp]
