Optional Huobi’s auth private key signature param

This is a security feature that was introduced briefly, where you were
required to upload a public key while generating your api keys, and for
authentication you had to use your private keys to sign the request and
send it through this “PrivateSignature” param.

This security feature was rolled back and it is not mentioned anymore
in Huobi’s documentation.

For backwards compatibility purposes we should still keep this feature
though, they still seem to accept this parameter, I guess if you have
one of this old api keys, that was generated with a given public key,
you still have to send it.
This commit is contained in:
herenow
2018-09-29 19:25:38 -03:00
parent a2c5123c9e
commit 0fdf76d264
5 changed files with 30 additions and 22 deletions

View File

@@ -748,6 +748,7 @@
"authenticatedApiSupport": false,
"apiKey": "Key",
"apiSecret": "Secret",
"apiAuthPemKeySupport": false,
"apiAuthPemKey": "-----BEGIN EC PRIVATE KEY-----\nJUSTADUMMY\n-----END EC PRIVATE KEY-----\n",
"apiUrl": "NON_DEFAULT_HTTP_LINK_TO_EXCHANGE_API",
"apiUrlSecondary": "NON_DEFAULT_HTTP_LINK_TO_EXCHANGE_API",
@@ -787,6 +788,7 @@
"authenticatedApiSupport": false,
"apiKey": "Key",
"apiSecret": "Secret",
"apiAuthPemKeySupport": false,
"apiAuthPemKey": "-----BEGIN EC PRIVATE KEY-----\nJUSTADUMMY\n-----END EC PRIVATE KEY-----\n",
"apiUrl": "NON_DEFAULT_HTTP_LINK_TO_EXCHANGE_API",
"apiUrlSecondary": "NON_DEFAULT_HTTP_LINK_TO_EXCHANGE_API",
@@ -1297,4 +1299,4 @@
"supportedExchanges": "ANX,Kraken"
}
]
}
}