Then you grab your secret key and your query string and hash that using SHA-1: SHA-1(key+queryString) In order to generate a URL with the following options: width: 640įirst you build the query string: width=640&height=480&fps=4&callback=http%3A%2F%2Fplaceit%2Enet%2Fexample%2Dendpoint%2F1234 Once a client registers an application, he will obtain a ClientID and Given the following example, we can identify what part correspond to the The query string is parsed and a new session is armed with the sent The identity of the client by confirming the authenticity hash against When this URL is clicked by a user, recordit will catch it and confirm Secret key according to the section on authenticating requests. TheĬonfirmation hash is generated by hashing the query string and the His clientId, the confirmation hash and finally the query string. The key should be kept secret.Īrmed with a ClientID and key, the user then generates a URL by placing They will be given a ClientID and a secret key that they will use to Once the data for their app has been introduced, Registering +-+ request +-+Ī requester wishing to use the recordit URL API must request access via The authenticity tokens that must accompany every request Solution Blackbox Triggering +-+ triggered +-+ confirm +-+ In order to use the URL API, a client must first request a ClientID + Key with an identity server to prove that the client can indeed trigger Once this URL is caught, the app must confirm the client identity and This URL, besides the encoded options for width, height, fps andĬallback should include a unique identifier for the user, plus a special The query string to pass an indefinite amount of parameters to the app. The recordit URL scheme follows a similar form to magnet links by using
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |