tommyb42 said By Changing the last Line of Daniels Code to vOutput = $encode("URL", $concat("type=", vKeyType, "&ver=", vTokenVersion, $concat("&sig=", vSignature))) Finaly I Get The Http 200 Ok. Thanks all of you for your help.   

Thanks for your feedback. Good to hear that you've got it working now. I'm not sure what happened with my code example, but it seems that the editor converted the "&" to "&". I've corrected this now.

So you had you tried this: raw vskeyRaw string vskey vskeyRaw=$encode(“HMAC_SHA256″,”%%vshash”,”%%vsmaster”) vskey=$encode(“BASE64″,”%%vsKey”) I haven't digged into this now, but I found some testing I did some months ago, finding that SHA1 and HMAC_SHA256 works in Uniface, except for empty "" value. We tested somehow like this: variables raw tRaw string tBase64 endvariables debug ;tRaw = $encode("HMAC_SHA256", "f95fa8b05c6747ffff790d7c4444f6d8|POST|https://changedapi/changed/changed|1446723703|983fchanged71a8f9e|2jmj7l5rchangedK/YBwk=", "dj4qUsjchangedTvchangedM=") ;tBase64 = $encode("BASE64", tRaw) tRaw="" tRaw = $encode("SHA1", tRaw) tBase64 = $encode("BASE64", tRaw) perhaps you can learn something from this. Regards RogerW.

So, application/json wasn't fixed (from what I understand) until 9.7.2. (https://unifaceinfo.com/forum/uniface9/restful-service-in-uniface/) What does the IIS error logs say? Knut

9.7.1 and also tested with 9.7.3

What's the Uniface version in question?

Hi Roger ,  The Problem actualy it is on the authorization token, by the way it is produced from uniface and how it's read from the cosmos db.

I've done something similar, using a somehow different syntax for the sending. But that's probably the same functionality. ; Call the UHTTP.SEND operation vUHTTP->SET_FLAGS(8) ;Send headers with all methods. By default, headers are sent only on the POST and PUT methods. vStatus = vUHTTP->SEND(vURI, "GET", "", "", vHeaders, vContent, vResponse) Can't see any other way than comparing what you send from VS to what you send from Uniface. Regards RogerW.

Yes Iain , i ve tried  same error responce.

I've no major clue, but $encode returns a raw value. Have you tried making the vskey variable a raw datatype?

Hi Knut ,  The error message is : "{"code":"Unauthorized","message":"The input authorization token can't serve the request. Please check that the expected payload is built as per the protocol, and check the key being used. Server used the following payload to sign: 'get dbs tue, 22 may 2018 7 :47:08 gmt ' ActivityId: c33075ef-a447-4cae-b803-a24a62b60d8e, Microsoft.Azure.Documents.Common/1.20.108.4"}"

By Changing the last Line of Daniels Code to vOutput = $encode("URL", $concat("type=", vKeyType, "&ver=", vTokenVersion, $concat("&sig=", vSignature))) Finaly I Get The Http 200 Ok. Thanks all of you for your help. 

And here's the result from the call: vsResponse = "HTTP/1.1 200 Ok" vsHttpContent = "{"_rid":"","Databases":[{"id":"ToDoList","_rid":"QfBiAA==","_self":"dbs\\/QfBiAA==\\/","_etag":"\\"00000000-0000-0000-f1b9-b26f9bc401d3\\"","_colls":"colls\\/","_users":"users\\/","_ts":1526985798}],"_count":1}"

Hi Thomas, This is working for me:

Please note that I had to adjust the time (my time zone is UTC+1). Hope this helps. Daniel

Hi Daniel,  You are right but still i am getting the same error. I will investigate it further i'll come back. Anyway thanks a lot for your help.

Ok, this ” + Date.toLowerCase() + “ ” + “” + “ “; was a bit strange in your example. But you can probably just ignore + "" + as Daniel has done. The fact that Uniface encodes an empty string wrong, didn't have anything with your problem to do. Regards RogerW.

Hi Thomas, There are two issues here: 1. The $encode function expects the key as RAW and not BASE64 2. The default (internal) new line character is CR (0x0D) and not LF (0x0A) When I use the example encoding from the mentioned API reference page (https://docs.microsoft.com/en-us/rest/api/cosmos-db/access-control-on-cosmosdb-resources) then the following code will give the same result:

I hope this helps. Regards, Daniel

Hi, There is not a problem with the encoding, except if you try to encode an empty/null string. Otherwise we have got the same result as with VS. Ok, now I saw what you meant. Strange.... You probably have to hardcode the "", but I'm not sure what + "" + "" really mean..... Regards RogerW.

Hi Roger ,  If there is a problem with the "" for  HMAC_SHA256 encoding  perhaps this is a probably answear beacause according the instructions you have to pass this to the key  StringToSign = Verb.toLowerCase() + " " + ResourceType.toLowerCase() + " " + ResourceLink + " " + Date.toLowerCase() + " " + "" + " ";