You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I cannot get past this, the return Redirect(authUrl); fails and I get a XML message, "An error has occurred.". I'm connecting to the live server which is HTTPS. I verified the clientID as well as the other variables is the authUrl string. I verified the API Client setup on the live site is active and the call back url is: http://localhost:49676/token. When I change to debug and run nopcommerce with the api plugin locally it works, even if I use the same db as the live site. So I know it can create the authorization code. I'm pretty sure the issue is with getting it to refresh the token but, I can't get it past this point to refresh it. The return doesn't throw a direct exception, it continues on to the outer bracket and then throws the error on the api application's web page.
Any ideas are greatly appreciated.
This image is after trying to use the RestSharp solution;
The text was updated successfully, but these errors were encountered:
I cannot get past this, the return Redirect(authUrl); fails and I get a XML message, "An error has occurred.". I'm connecting to the live server which is HTTPS. I verified the clientID as well as the other variables is the authUrl string. I verified the API Client setup on the live site is active and the call back url is: http://localhost:49676/token. When I change to debug and run nopcommerce with the api plugin locally it works, even if I use the same db as the live site. So I know it can create the authorization code. I'm pretty sure the issue is with getting it to refresh the token but, I can't get it past this point to refresh it. The return doesn't throw a direct exception, it continues on to the outer bracket and then throws the error on the api application's web page.
Any ideas are greatly appreciated.
This image is after trying to use the RestSharp solution;
The text was updated successfully, but these errors were encountered: