I want to create Heroku new app, but every time shows an error like 'Invalid credentials provided'.
Related
When attempting to log in to Heroku it will not allow me to log in and get an error message 'MISSING SESSION'
I can't log a call with Heroku support as I can't log in!
I have 2nd authentication turned on and have entered the code on the authenticator app, the log in accepts this as a big green tick appears, but then I get the error message
Has anyone had had this error when attempting to log in and is there a solution?!!
Just make sure to log out from all previous sessions still opened, on all your devices.
I’ve been trying to login to HEROKU CLI on a headless Ubuntu. So, I don’t have a chance to open a browser. That’s why, I need to login with credential or any other method but there are only two login options which are browser, credentials.
Is there anybody face with the same problem?
Command:
heroku login -i
Error Message:
› Error: Your account has MFA enabled; API requests using basic authentication with email and password are not supported. Please generate an authorization token
› for API access.
›
› Error ID: mfa_required
PS: The Heroku doesn’t allow me to disable MFA.
Shanshan Chen is basically right, but given the specifics of your issue you're still going to need the -i flag. I have had the same issue and was able to log in successfully using these steps:
Run heroku login -i
Enter your email address as normally
For the password, use your Heroku account API Key (see below)
Try heroku login and use API key as the password. Feel free to refer to
Not able login to Heroku account from command line
I am trying with Amplify and trying to create my first react application, to just fetch simple Ride model.
I am always getting 401 unauthorised error on localhost and after hosting to S3.
errorType: "UnauthorizedException"
message: "You are not authorized to make this call."
#SlackGadget's solution was essentially correct.
The default expiration time of the AppSync API key is 7 day, meaning if you do not set this in your initial congif of your Amplify build or use a different type of authentication, then your API will expire after 7 days. If you deploy within this timeframe then a new key is generated, but there is no real warning without checking AppSync.
To check follow these steps:
Go to AWS AppSync
Click on the app in question
Click Settings in the side nav
Check the key against what appears in your aws-exports.js file, if it has expired this will be the issue.
Solution:
To initially fix it, re-deploy you app from the Amplify console to get it up and running an prevent the 401 error
Then update the API locally, go to your <project-root>/amplify/backend/api/<api-name>/parameters.json file and add a APIKeyExpirationEpoch key. This take an expiration time in seconds of the key. You can then deploy this and the new key will have a new expiration date.
You can also update the expiration key in the AppSync setting
Here are the docs for overwriting the Amplify parameters: https://docs.amplify.aws/cli-legacy/graphql-transformer/resolvers/#custom-resolvers
I am deploying an app on Heroku that uses Google OAuth2. When I test the app, I go to the auth url (/auth/google) and I see the following error message (note that I replaced domain name with *** just for posting here:
That’s an error.
Error: invalid_client
The OAuth client was not found.
Request Details response_type=code
redirect_uri=https://****.com/auth/google/callback scope=profile email
client_id=process.env.GOOGLE_CLIENT_ID That’s all we know.
I have looked at the following questions before posting and have been trying to debug for several hours:
Error: invalid_client with Google Apps API OAuth2
invalid_client in google oauth2
I have tried to do the following:
Ensure there are no spaces before and after the values in Heroku
The consent screen in Google Console has the name and email address completed
I have renamed the app within Google Console
I have deleted the key/value from Heroku and re-created
Despite all this, I am unable to fix this. Any ideas on what I maybe missing?
The answer is in the question.
Google can't find any reference to your client, which is identified by the client_id in the URL. Instead of a valid client_id (which looks something like "40740878192.apps.googleusercontent.com") you have given a client_id of "process.env.GOOGLE_CLIENT_ID". It looks like a bug in your code that instead of using process.env.GOOGLE_CLIENT_ID as a variable, you have used it as a literal.
I got this error when I create new client secret in new project.
That’s an error.
Error: restricted_client
Unregistered scope(s) in the request: https://www.googleapis.com/auth/youtube.readonly
Request Details
access_type=offline
response_type=code
client_id=487794563386-mujtj6b5iatnmvdailldn468gg028p8g.apps.googleusercontent.com
redirect_uri=http://localhost:61515/authorize/
scope=https://www.googleapis.com/auth/youtube.readonly
That’s all we know.
How could I fix that ?
403 errors are errors with the users access. The user you are currently authenticated with does not have permission to do what you are trying to do in your case it appears to have something to do with the following scope.
https://www.googleapis.com/auth/youtube.readonly
Its hard to know what you are doing without seeing your code. I suggest you attempted to authenticate your user again. IF you changed the secret then its not going to work with a refresh token generated by another secret.
I am going to contact Google to be sure that there hasnt been any changes recently. I cant see anything in the change logs myself. There may have been a stealth change that they didnt release.
Status