Chris Davis
2018-10-01 15:56:56 UTC
Hi All
I am still pluging away at this and making steady progress.
I have now got my access token and secret and can successfully make queries against the API endpoint using Postman.
https://www.mywebsite.com/api/rest/products?page=1
I can make the same request from VFP and if I sign the request using PLAINTEXT then it works no problem.
If I attempt to sign it using HMAC-SHA1 then I get the following error ...
{"messages":{"error":[{"code":401,"message":"oauth_problem=signature_invalid"}]}}
I have used the same VFP code borrowed from the OAuth project on VFPX github to get as far as the access token so I am happy that the signing code works so I think it must be something I am either including or excluding from the string that gets signed which is causing the issue.
Can anyone spot anything obvious ...
GET&https%3A%2F%2Fwww.mywebsite.com%2Fapi%2Frest%2Fproducts&oauth_consumer_key%3Dd5740bb1a40426a34917b58153b5d060&oauth_nonce%3D49878452BA6F410EA566452C71B9F4CD&oauth_signature_method%3DHMAC-SHA1&oauth_timestamp%3D1538408837&oauth_token%3D22cad6515e48df11001a14e335477188&oauth_version%3D1.0&page%3D1
Any help appreciated.
Thanks
Chris.
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
_______________________________________________
Post Messages to: ***@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/***@CWLP265MB1668.GBRP265.PROD.OUTLOOK.COM
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
I am still pluging away at this and making steady progress.
I have now got my access token and secret and can successfully make queries against the API endpoint using Postman.
https://www.mywebsite.com/api/rest/products?page=1
I can make the same request from VFP and if I sign the request using PLAINTEXT then it works no problem.
If I attempt to sign it using HMAC-SHA1 then I get the following error ...
{"messages":{"error":[{"code":401,"message":"oauth_problem=signature_invalid"}]}}
I have used the same VFP code borrowed from the OAuth project on VFPX github to get as far as the access token so I am happy that the signing code works so I think it must be something I am either including or excluding from the string that gets signed which is causing the issue.
Can anyone spot anything obvious ...
GET&https%3A%2F%2Fwww.mywebsite.com%2Fapi%2Frest%2Fproducts&oauth_consumer_key%3Dd5740bb1a40426a34917b58153b5d060&oauth_nonce%3D49878452BA6F410EA566452C71B9F4CD&oauth_signature_method%3DHMAC-SHA1&oauth_timestamp%3D1538408837&oauth_token%3D22cad6515e48df11001a14e335477188&oauth_version%3D1.0&page%3D1
Any help appreciated.
Thanks
Chris.
--- StripMime Report -- processed MIME parts ---
multipart/alternative
text/plain (text body -- kept)
text/html
---
_______________________________________________
Post Messages to: ***@leafe.com
Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox
OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/***@CWLP265MB1668.GBRP265.PROD.OUTLOOK.COM
** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.