GoogleAppEngine sign-in failed - google-app-engine

I am afraid I don't have much information on this problem, other than that I cannot deploy/update an application with GAE anymore.
Every time when asked for email and password, I correctly enter them (as I always have done), and I get a Sign-in Failed message.
I tried it two ways, 1) with GoogleAppEngineLauncher application. I first get a panel saying: "Error, failed; auth error", and after I close this panel there is message in red in the sign-in panel, saying: Sign-in Failed. This is a hyperlink, which, when I click it, brings me to a browser page where I am asked to re-enter my password for my google-account. I enter the same password, and I get logged in normally.
If I click on the Dashbord button it brings me to the correct app-engine page of my application.
The second way is command-line:
appcfg.py update /my_app_name
which results in:
10:48 AM Application: my_app_name; version: 1
10:48 AM Host: appengine.google.com
10:48 AM
Starting update of app: my_app_name, version: 1
10:48 AM Getting current resource limits.
Email: my_email#gmail.com
Password for my_email#gmail.com:
Invalid username or password.
However, I am 100% sure I am using the correct login details.
Well, I hope someone can make sense of this! thanks!
edit: this is the error panel I get when I try to deploy with the launcher app

You can visit https://www.google.com/settings/security and then enable "Access for less secure apps" . It works for me.

You could try uploading with OAuth2:
appcfg.py --oauth2 update /my_app_name
See for more info:
https://cloud.google.com/appengine/docs/python/tools/uploadinganapp#Python_Password-less_login_with_OAuth2

I had a similar issue, but I'm using maven to deploy, not appcfg. I know that I had to go in my "C/users/ME/" and delete a file called ".appcfg_oauth2_tokens_java", and it worked afterwards.
Having researched the issue, it seems to appear when you have multiple accounts logged in at some point. The system keeps a copy of one of your other accounts and tries to deploy using this. Deleting the appcfg_oauth token forced me to "re validate" my credentials

Related

Notes Federated Login not downloading in memory ID file - Entry not found in index

We have setup Notes federated login to provide a single-signon for Notes clients from Active directory. and there seem to be a problem when getting the "in memory" ID file from the Vault.
Here is the scenario
User start Notes (tried both v9 and V10) for the first time
Enter password in the Login screen for the local id file.
Message prompt "ID file is now downloaded for Notes Federated Login"
User click "OK" and a new message show up "Server Error - Entry not in index"
User click "OK" and then the passsword prompt for the local id file is displayed.
So, in short there seem to be a problem when downloading from the Vault but the error message do not really say much.
We have enabled all the client debug options and checked the server logs but nothing really tells us what is wrong.
All we get is this:
An issue that failed to authenticate was reported from the server / domain server: Entry not in index
Id-file is already in use and can't be changed
I can't diagnose the issue from reading your problem description. I suggest you open a support ticket with the steps to reproduce. ERR_NOT_FOUND (not found in index) is a very common return value in Domino, often even being benign. But in the benign cases it is handled by the calling code.
So it's hard to know what method/function threw the error or what the stack was at the time. Hence the advice to open a support ticket.

HTTPError: 400 client Error: user 'x' has no verified email addresses while pushing python package to pypi

HTTPError: 400 Client Error: User 'sampleuser' has no verified email addresse
s, please verify at least one address before registering a new project on PyPI.
See https://pypi.org/help/#verified-email for more information. for url: https:/
/upload.pypi.org/legacy/
The above error I am getting when I run " twine upload dist/* " command
Alright, I figured out:
You need to login to https://pypi.org/ instead of the old https://pypi.python.org/pypi.
https://pypi.org shows a "pre-production" warning on top, but that doesn't matter. Login to your account, go to account setting, and verify your email. The old site doesn't have a way to check whether your email is verified or not.
I am experiencing the same problem right now while trying to update a repo that's already on PyPi.
But I found this link on my profile page and on clicking it I read
we are experiencing issues with pypi.org and the upload.pypi.org
endpoint. we're actively working to resolve the issue and will update
here as we're able.

ClientLoginException from appcfg.sh

I am attempting to upload a new version of a Google App Engine Application with appcfg.sh
upload but get the following exception:
com.google.appengine.tools.admin.ClientLoginServerConnection$ClientLoginException:
Email "...#gmail.com" and password do not match.
When prompted, I use the same Email address (...#gmail.com) and password that works just fine for logging into Google Developers Console e.g. using Safari.
Could this be a problem with my terminal settings? (I am using OS X Yosemite. If I type the password on the command line it appears as expected.)
I'd recommend the "password-less login with oauth2" explained at https://cloud.google.com/appengine/docs/python/tools/uploadinganapp#Python_Password-less_login_with_OAuth2 .
Just run appcfg.py --oauth2 with whatever command you require, and you'll be asked, once, to authorize your Google userid in your browser; then, the credentials are stored in file .appcfg_oauth2_tokens, and used thereafter. The page above goes into details about how to control the authorization process more finely, but, for me, the simple approach I'm summarizing here has been quite satisfactory.

Why is the Google App Engine SDK for Windows flagged as a security risk by Google?

I'm using app engine for windows and when I try to deploy the app to the cloud, I'm asked for a username and password. When I enter the username and password, I get the following error:
Password for xxxxx#xxxxx.xxx: Invalid username or password.
2014-11-06 18:48:41,628 ERROR appcfg.py:2417 An error occurred processing file '': HTTP Error 401: > > > Unauthorized. Aborting.
Error 401: --- begin server output ---
Must authenticate first.
--- end server output ---
2014-11-06 18:48:41 (Process exited with code 1)
Then, I got an email from Google stating, that an attempt was made to login my account and it was blocked. If it wasn't me, take the following steps. But, if it was me:
If this was you
You can switch to an app made by Google such as Gmail to access your account (recommended) or > change your settings at https://www.google.com/settings/security/lesssecureapps so that your >account is no longer protected by modern security standards.
Any ideas? I'd hate to lower my security standards. Is this some sort of bug?
Use OAuth2 rather than a username and password to authenticate when uploading your app.
Looks like you are hitting the same issue as this guy.
As I told him there:
Go here under Account permissions -> Access for less secure apps -> Settings make sure its set to enabled.
Otherwise you will have to use the console.
You might be accessing google servers via some proxy. And google being a LOCATION geek, over-intelligently blocks you. Try authenticating it once, and it should not be a problem from then on, provided proxy or IP addresses does not change frequently. NOTE: i might be completely wrong as well.

Google_AuthException : invalid_grant

I'm trying to setup the config.php with my values but I get this fatal error:
Fatal error: Uncaught exception 'Google_AuthException' with message 'Error fetching OAuth2 access token, message: 'invalid_grant'.
I entered the client ID, secret, simple API key, location and sqlite database as the documentation says here:
https://developers.google.com/glass/quickstart/php
Any idea of what I'm doing wrong?
Thanks in advance!
This happens when the URL where you're hosting your Glassware is not listed as a valid OAuth 2.0 redirect URI on the API console. Follow these steps to resolve it.
First, determine your OAuth 2.0 redirect URI. This is where traffic goes at the end of the OAuth dance. The correct value depends on where you're running the php quick start. If you're running it on a local web server, it's likely to be http://localhost/mirror-quickstart-php/oauth2callback.php. If you're running it on example.com, it might be https://example.com/oauth2callback.php.
Go to the API console. This link will lead you to the right panel (services), but double check that you're on the correct project.
Scrolling down you should see a section of the page that looks like this: . Click on 'Edit Settings...'.
This triggers a pop-up where you can enter your OAuth redirect URIs. Add your redirect URI to the top text area. Make sure to put each URI on its own line.
Reload the page for the PHP Quick Start and everything should work.
If you're still having an issue, please share the full error message on the page and the value you have for the base url in config.php.
If you're getting the invalid_grant error from Google : Instead of using the client ID from google developer console as your value for client ID in the code, try using the email address value from developer console. This is actually what they expect. So, to confirm - the value for Client ID should be the value from developer console ending #developer.gserviceaccount.com
Had similar problem in Windows PS dotnet environment when trying to connect to DialogFlow Google Cloud Project recently and it appeared to be intermittent fault but it turned out to be global $env:GOOGLE_APPLICATION_CREDENTIALS in windows PowerShell was pointing to a key file set when first setup access to GCloud days before and since regenereated keys in GCP Console
After generating new key file and setting it with new generated key file using $env:GOOGLE_APPLICATION_CREDENTIALS="[Path_To_JSON_Key_File]" the problem went away but fix only lasted as long as the window was open, then after a while ran $env:GOOGLE_APPLICATION_CREDENTIALS on a newly opened PS window and noticed it was still pointing to the old key file!
setting the system environment variable GOOGLE_APPLICATION_CREDENTIALS to the value of [Path_To_JSON_New_Key_File] fixed it, all newly opened PS windows had the correct key file and authenticated correctly using Service Account and .Net Google Cloud API calls worked after that

Resources