I followed the sound experience guideline to set up environment and authorization. When I try to get a new access token, this error keeps popping up. I wasn't sure what it means. I'm following exactly the same step as the guide, This is the error:-
An error occurred while processing your request.
Reference #97.6d06d217.1539357275.34c5f2e
Related
I am trying to implement auth0 in a very basic spring-boot-application based on maven. This is the error that I get:
com.auth0.IdentityVerificationException: An error occurred while exchanging the Authorization Code for Auth0 Tokens
When running the original tutorial-project everything works fine. The error occurs only in my custom application. Basically I copied all the files from the tutorial-project into my application. Nevertheless I run into this error...
further down the exception I see a
com.auth0.exception.APIException: Request failed with status code 401: Unauthorized
Solved it:
The client-secret was wrong. Actually there is a space at the end of my client-secret, which I accidentally removed. Wow.
Gmail OAuth API has been working well until Feb 17th, and POST /o/oauth2/token randomly returns this error while refreshing OAuth token:
Parameter not allowed for this message type: redirect_uri
The error occurs about 1 out of 10 times. What's strange is that, after receiving this error, the next exact same request succeeded. So this is not related to "redirect_uri" as suggested by the error message.
"Parameter not allowed for this message type" has been reported in other StackOverflow posts, but they are all persistent errors and can be resolved by fixing the parameters. While the error we got is temporary. The 10% rate is costly to the user experience.
Has anyone seen similar behavior lately?
It seems Google has recently changed the url for getting a new access token from a refresh token. The older url was https://accounts.google.com/o/oauth2/token and the new one is https://www.googleapis.com/oauth2/v4/token.
Also I remember that redirect_uri was previously among the parameters for getting a new access token, but it no longer seems to be there: https://developers.google.com/identity/protocols/OAuth2WebServer#offline. Just look at the HTTP/REST example.
It is possible that just removing redirect_uri works even with the older url, but I think it is wise to both change the url and remove redirect_uri.
I'm unable to add a comment above, but we've been seeing a similar issue too with intermittent failures on oauth.
Removing the "redirect_uri" worked, though that makes me nervous since the documentation https://developers.google.com/identity/protocols/OAuth2WebServer says to include it.
What does work, though, and allows us to keep the "redirect_uri" is updating our url from https://accounts.google.com/o/oauth2/token to https://www.googleapis.com/oauth2/v4/token
I am creating an object in parse (using back4app parse server for this).
I get the following error when I run the choreo in temboo.
A HTTP Error has occurred: The remote server responded with a status
code of 401. Typically this indicates that an authorization error
occurred while attempting to access the remote resource. The data
returned from the remote server was: {"error":"unauthorized"} . The
error occurred in the HTTPSend (Parse) step.
That 401 error might indicate that the Id or Keys are not correct. Maybe it could be a good idea to double check them.
Also, what is the host and path for the API Request that you're doing with Temboo (I'm not acquainted with it)? If you're not using the correct ones it might cause problems too.
Make sure you're reaching something like this:
https://parseapi.back4app.com/classes/Your_Class_Name
I have code which is calling SEMRush API and it is working fine for a while, and then suddenly I stared getting 403 on API call with SEMRush error:
ERROR 135 :: API REPORT TYPE DISABLED
The API endpoint which I am calling is:
http://us.api.semrush.com/?action=report&type=phrase_this&key={xxxxxx}&export=api&export_columns=Ph,Nq,Cp,Co,Nr&phrase=sport
I cannot find anything about this error in their documentation.
Please does anyone know what this error means and how to resolve it?
Try updating your API call to the newer method. According to their documentation the database is no longer a subdomain and rather a parameter.
So instead of http://us.api.semrush.com/?action=report&type=phrase_this&key={xxxxxx}&export=api&export_columns=Ph,Nq,Cp,Co,Nr&phrase=sport
Try http://api.semrush.com/?action=report&type=phrase_this&key={xxxxxx}&export=api&export_columns=Ph,Nq,Cp,Co,Nr&phrase=sport&database=us
I've ran into a problem and I don't know how to fix it. I've searched around to see if other people are having this issue but I can't find anything relative to my error. I'm using the OAuthSample example app. The google login works great but not the twitter login. The error that I'm getting is
Authentication error: Error Domain=com.google.HTTPStatus Code=401 "The operation couldn’t be completed. (com.google.HTTPStatus error 401.)"
I've filled in myConsumerKey and myConsumerSecret correctly so I don't understand what the deal is. The modal drop down window will not even drop down and load the url page so I can put the twitter username and password.
I've figured it out. You have to put a callback url in the twitter settings or the authentication will fail.