4. HTTP API to Open Door HTTP API Open Door Authentication: The authentication is using Challenge/Response encryption mode. After the successful authentication by the administrator, each later on operations will be accepted and successful ONLY when the correct authentication information is included inside the request header. = Values Description cmd= 0: Step 1 1: Step 2 authcodestring= md5(ChallengeString:remote_pin
assword); idcodestring= From authentication’ step 1 opt_type= 1: open door 2: close door The authentication process is as following: Step 1: Client ➔ Server GDS37XX HTTP API P a g e | 114 Version 1.0.0.23 [http|https]:///goform/apicmd?cmd=0&user=admin Server ➔ Client 0 5c0e1f55b54be2d0c56004ba349fb726 UM1NWDJYC19LOEYQRWNA Step2: Client ➔ Server [http|https]:///goform/apicmd?cmd=1&user=admin&authcode=&idcode=&type=opt_type NOTE: The rule for authcodestring listed below: authcodestring = md5(ChallengeCode:remote_pinassword); idcodestring = The node value of “IDCode”, such as “UM1NWDJYC19LOEYQRWNA” above example. opt_type = 1: open door, 2: close door ➢ The “ChallengeCode” is the returned string from Server in Step 1. ➢ Remote_pin is “Remote PIN to Open Door” ➢ Password is the login password of the device (GDS37xx). ➢ Authcodestring must be length of 32 in lowercase hex as in MD5 hash. ➢ The RED part is the authentication message returned by the Server after successful authentication. ➢ This part of the message must exist in the message header before all later on operations can run successfully. If authentication OK, the return message like this: GDS37XX HTTP API P a g e | 115 Version 1.0.0.23 HTTP/1.0 200 OK Content-Type: text/xml;charset=UTF-8 0 Authentication OK If authentication Failed, the return message like this: HTTP/1.0 200 OK Content-Type: text/xml;charset=UTF-8 1 Authentication error If the HTTP API to open door disable, then the return message like this: HTTP/1.0 200 OK Content-Type: text/xml;charset=UTF-8 1 HTTP API open door function is disable If the remote open door PIN is null, then the return message like this: HTTP/1.0 200 OK Content-Type: text/xml;charset=UTF-8 1 Authentication error. Remote PIN is null GDS37XX HTTP API P a g e | 116 Version 1.0.0.23 Notes: • The RED part is the authentication information returned by the Server after successful authentication. • This part of the information must exist in the message header before all later on operations can run normally. • The user must be “admin”, others do not have the privilege. • Default Validity of the idcodestring come from step 1 is 30 seconds, it is mean that user must finish the step 2 in 30 seconds, or the idcodestring will timeout and invalid. (This parameter can ONLY be configured via P Value which is P15428) For example, if you want to set it to 150 seconds, you will need to apply this command: http:///goform/config?cmd=set&P15428=150 • The “type=1” means that the HTTP API is for open door. • Authcode string length must be 32 in lowercase hex as in MD5 hash.
Can you show me how to use this format in Big5 to open the door on a grandstream gds3710
assword); idcodestring= From authentication’ step 1 opt_type= 1: open door 2: close door The authentication process is as following: Step 1: Client ➔ Server GDS37XX HTTP API P a g e | 114 Version 1.0.0.23 [http|https]:///goform/apicmd?cmd=0&user=admin Server ➔ Client 0 5c0e1f55b54be2d0c56004ba349fb726 UM1NWDJYC19LOEYQRWNA Step2: Client ➔ Server [http|https]:///goform/apicmd?cmd=1&user=admin&authcode=&idcode=&type=opt_type NOTE: The rule for authcodestring listed below: authcodestring = md5(ChallengeCode:remote_pinassword); idcodestring = The node value of “IDCode”, such as “UM1NWDJYC19LOEYQRWNA” above example. opt_type = 1: open door, 2: close door ➢ The “ChallengeCode” is the returned string from Server in Step 1. ➢ Remote_pin is “Remote PIN to Open Door” ➢ Password is the login password of the device (GDS37xx). ➢ Authcodestring must be length of 32 in lowercase hex as in MD5 hash. ➢ The RED part is the authentication message returned by the Server after successful authentication. ➢ This part of the message must exist in the message header before all later on operations can run successfully. If authentication OK, the return message like this: GDS37XX HTTP API P a g e | 115 Version 1.0.0.23 HTTP/1.0 200 OK Content-Type: text/xml;charset=UTF-8 0 Authentication OK If authentication Failed, the return message like this: HTTP/1.0 200 OK Content-Type: text/xml;charset=UTF-8 1 Authentication error If the HTTP API to open door disable, then the return message like this: HTTP/1.0 200 OK Content-Type: text/xml;charset=UTF-8 1 HTTP API open door function is disable If the remote open door PIN is null, then the return message like this: HTTP/1.0 200 OK Content-Type: text/xml;charset=UTF-8 1 Authentication error. Remote PIN is null GDS37XX HTTP API P a g e | 116 Version 1.0.0.23 Notes: • The RED part is the authentication information returned by the Server after successful authentication. • This part of the information must exist in the message header before all later on operations can run normally. • The user must be “admin”, others do not have the privilege. • Default Validity of the idcodestring come from step 1 is 30 seconds, it is mean that user must finish the step 2 in 30 seconds, or the idcodestring will timeout and invalid. (This parameter can ONLY be configured via P Value which is P15428) For example, if you want to set it to 150 seconds, you will need to apply this command: http:///goform/config?cmd=set&P15428=150 • The “type=1” means that the HTTP API is for open door. • Authcode string length must be 32 in lowercase hex as in MD5 hash.Can you show me how to use this format in Big5 to open the door on a grandstream gds3710
Comment