I can't get acccess to Tuya cloud API - api

I have been struggling with connecting to Tuya cloud API. Testing in postman gives me this result:
enter image description here
The things I have done:
I conntected the device to Tuya developer account.
I configured my developer account and have acccess to tuya IOT service.
I set up testing enviroment as shown in this link: https://developer.tuya.com/en/docs/iot/set-up-postman-environment?id=Ka7o385w1svns
I made sure that i have turned off the cloud IP Allow list.
Yet still that error occurs although when I send a request through API Explorer on the tuya site everything works correctly. Can someone know the origin of this error?

Related

Azure App Service Oauth failure after Mobile Service migration

Up to this point, I had a functioning Azure Mobile Service with service-directed OAuth working nicely for Google. I tried to rehost the mobile service as an app service since mobile services are deprecated. I also have an HTML/JS web app that accesses my service through the MobileServiceClient JS client. This is where the fun starts.
After changing the redirect address to the appropriate app service address in the Google API manager, I get a message saying I'm successfully logged in in a new popup window: .
Clicking on "Return to Website" takes me to the address of my app service, not the app that initiated the OAuth request, and if I close this window, the MobileServiceClient throws a "cancelled" exception and I don't get my credentials.
What am I missing or what changed that I need to account for?
Thanks!
It turns out that this particular behavior happens when using an older version of the MobileServiceClient JS library. Replacing the 1.2.7 version with the 2.0.0beta version fixed this. To get the whole OAuth flow working, I also needed to add the appropriate addresses to the allowedExternalRedirectUrls node of the config/authsettings node through the Azure Resource Explorer. If there is a nicer way to do it than through the resource explorer, I don't know what it is.

The Google Maps API server rejected your request. This IP, Site or mobile application is not authroised to use this API key

I have implemented the Google maps iframe embed api to my website, the map API is working correctly on desktop web browsers as well as Google Chrome for mobile.
However when i attempt to view the page of my site with the API on in mobile safari on iphone i get an error saying;
"The Google Maps API server rejected your request. This IP, Site or mobile application is not authroised to use this API key".
I Have enabled Google Map API for IOS on the google developer console and the issue still hasnt gone away. As i said the API works fine on other mobile browsers.
Does any one have any suggestions how to fix this?
Thanks, Martin
Did you create a new Client ID?
Handheld devices require "Installed Application" Client ID, not "Web Application. "

Logging Analytics API

I wrote an application that downloads data from Analytics API. I didn’t have problem with login I used the OAuth 2.0 on my first computer, the problem is that now I’ve changed to my laptop, the authentication doesn’t work correctly.
The program use the next url for obtain the authentication:
https://accounts.google.com/o/oauth2/auth?client_id=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.apps.googleusercontent.com&redirect_uri=http://localhost:53636/Callback&response_type=code&scope=https://www.googleapis.com/auth/analytics.readonly
If I put this url in the old laptop the login works, but If I use the same url for login in the new laptop only obtain a access without connection.
I don’t understand why I get different results depends on the computer.

PayPal - switching from Sandbox to Live account using REST API

We tested our web application successfully using a sandbox REST API account (and test credentials).
When we wanted to put the application into production (using REST API live credentials visible on the same PayPal web site where the sandbox/text credentials were shown), we received an error from the production PayPal server on a live credit-card transaciton:
Error code : 401 with response : Server returned HTTP response code: 401 for URL: https://api.paypal.com/v1/payments/payment
We have a Business Account that is not yet 100% verified (75% verified at the moment), so we are not sure if this is caused by some technical issue or the fact that the account is not yet 100% verified.
PayPal web site is quite confusing and the process of moving the app from test to production is not clearly explained. It seems that they are migrating from some old web sites to new ones and the user is prompted to login multiple times, redirected to different URL-s... E.g. we can see our application test and live credentials on the developer.paypal.com, but not on apps.paypal.com where no apps are listed, even though the same user is logged in (owner of the business account)???
For future readers, you have to use Live Credentials, on https://developer.paypal.com go to My apps and in App details there is a link at a bottom of the page :
Click on that link and you will see live credentials.
You now click on your sandbox application and then click live at the top of the screen to get your live credentials.
For the PayPal REST api use the credentials provided on developer.paypal.com (new version of PayPal dev experience). Live calls require the account to be vetted which includes fully verified.

Facebook connect without Javascript in WiFi Hotspot

I am going to integrate the Facebook login access on my WiFi hotspot portal. Basically I would like the user to log on my portal using its Facebook credentials, in order to access the Internet via Hotspot.
The classical integration using connect-js via Javascript cannot work, since unauthenticated users cannot reach the Internet, and in this condition the browser cannot connect to Facebook.com.
Please, I would like to understand if there is a way, from my PHP portal, to send an HTTP post request to Facebook.com containing the users credentials. I just have made a test, but I have received the following response "For your security, never enter your Facebook password on sites not located on Facebook.com".
Thank you very much.
You need to manually-build-a-login-flow (relevant facebook documentation)
The below snippet is the crux of it however
https://www.facebook.com/v3.0/dialog/oauth?
client_id={app-id}
&redirect_uri={redirect-uri}
&state={state-param}