encodeURIComponent not working as expected for verification service on node server #16

r-vianna · 2017-04-15T16:39:48Z

Hello,

I am currently running a node/express server to do license verification for my application. I am having issues I was able to work around but it does not follow the guidelines provided so I wanted to check if I am missing something.

Currently I am getting the et parameter and base64 decoding it

var token = new Buffer(req.query.et, 'base64').toString('ascii');

Then according to the guidelines I need to url encode this to send it to the verification service. If I use encodeURIComponent as suggested, I get the following url (this is based off of the sample token provided in the docs).

token = encodeURIComponent(token);

This does not work (IsTest is false). However if I use some regex magic I do get a working response.

token = encodeURIComponent(token).replace(/%00|%0D/g, '').replace(/%20/g,'+');

https://verificationservice.officeapps.live.com/ova/verificationagent.svc/rest/verify?token=%3Cr%3E%0A++%3Ct+%0A++++aid%3D%22WA900006056%22%0A++++pid%3D%22%7B4FB601F2-5469-4542-B9FC-B96345DC8B39%7D%22%0A++++cid%3D%2232F3E7FC559F4F49%22%0A++++et%3D%22Trial%22%0A++++ad%3D%222012-01-12T21%3A58%3A13Z%22%0A++++ed%3D%222012-06-30T21%3A58%3A13Z%22%0A++++sd%3D%222012-01-12T00%3A00%3A00Z%22%0A++++te%3D%222012-06-30T02%3A49%3A34Z%22%0A++++ts%3D%220%22%0A++++test%3D%22true%22%2F%3E%0A++%3Cd%3EVNNAnf36IrkyUVZlihQJNdUUZl%2FYFEfJOeldWBtd3IM%3D%3C%2Fd%3E%0A%3C%2Fr%3E

Just wanted to clarify if I am doing something wrong or the documentation is out of date.

The text was updated successfully, but these errors were encountered:

PhilSmail · 2017-04-19T12:26:01Z

encodeURIComponent does work but you do need to format it correctly

If you do a search for URLencoder on bing the code behind that does the following, which works:
encodeURIComponent(n).replace(/%20/g, "+")

r-vianna · 2017-04-20T02:21:16Z

Thanks, I think it may be worth considering updating the docs to reflect the formatting aspect. From the following section:

The Office Store license verification web service also supports verifying add-in license tokens by using REST calls. To validate an add-in license by using REST, use the following syntax, where {token} is the add-in license token, encoded by a method that complies with RFC 2396. For example, the encodeURIComponent() function in JavaScript, or the Uri.EscapeDataString method in the .NET Framework:

It is not obvious (to me anyway) that extra steps are needed beyond using encodeURIComponent.
If you want I would be happy to write you a JavaScript example to use in the docs.

draisy · 2017-05-26T18:25:27Z

Hi @PhilSmail,

I ran into the same issue as @r-vianna above and was not able to resolve it with your suggestion of

encodeURIComponent(n).replace(/%20/g, "+"),

but if I do it this way

encodeURIComponent(token).replace(/%00|%0D/g, '').replace(/%20/g,'+'),

then it works successfully. Could the docs be updated to reflect this to save others from this same issue?

Thanks!

Lauragra assigned PhilSmail May 1, 2017

PhilSmail closed this as completed Apr 19, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

encodeURIComponent not working as expected for verification service on node server #16

encodeURIComponent not working as expected for verification service on node server #16

r-vianna commented Apr 15, 2017

PhilSmail commented Apr 19, 2017

r-vianna commented Apr 20, 2017

draisy commented May 26, 2017

encodeURIComponent not working as expected for verification service on node server #16

encodeURIComponent not working as expected for verification service on node server #16

Comments

r-vianna commented Apr 15, 2017

PhilSmail commented Apr 19, 2017

r-vianna commented Apr 20, 2017

draisy commented May 26, 2017