Login with Device Pin
Request to be POSTed to uri : /NorenWClientTP/PinAuth
Request Details :
| Parameter Name | Possible value | Description |
|---|---|---|
| jData* | Should send json object with fields in below list |
| Json Fields | Possible value | Description |
|---|---|---|
| uid* | User Id | |
| imei* | Imei or device unique fingerprin | |
| source* | Access type (API) | |
| dpin* | New pin in plain text | |
| vc* | Vendor code provided by noren team, along with connection URLs | |
| appkey* | Sha256 of uid | vendor_key | |
| apkversion* | Application version number | |
| ipaddr | global Ip of internet access |
Response Details :
Response data will be in json format with below fields.
| Json Fields | Possible value | Description |
|---|---|---|
| stat | Ok or Not_Ok | Login Success Or failure status |
| susertoken | It will be present only on login success. This data to be sent in subsequent requests in jKey field and web socket connection while connecting | |
| spasswordreset | Y | If Y Mandatory password reset to be enforced. Otherwise the field will be absent. |
| request_time | Response received time. | |
| emsg | "Invalid Input : MPIN not enabled for user",Also refer QuickAuth Error Messages list | This will be present only if Login fails. |
Sample Success Response :
{
"request_time":"17:01:45 27-05-2020",
"stat":"Ok",
"susertoken":"b0856b3f6c4bac657417fc95de3e2060567b8bd80665e0a8ab82bbde5c434936",
"lastaccesstime":"1590579105"
}
Sample Failure Response :
{
"request_time":"11:19:56 28-05-2020",
"stat":"Not_Ok",
"emsg":"Invalid Input : Mpin Invalid"
}