Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Authentication failures using Spanner with appengine:run for App Engine Standard J8 #2155

Closed
jabubake opened this issue Jun 15, 2017 · 4 comments
Closed

Authentication failures using Spanner with appengine:run for App Engine Standard J8 #2155

jabubake opened this issue Jun 15, 2017 · 4 comments
Assignees
@lesv
Labels
api: spanner Issues related to the Spanner API. auth priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. running on app engine type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@jabubake
Copy link
Contributor

Auth errors using both plugins in
mvn appengine:run : http://mvnrepository.com/artifact/com.google.cloud.tools/appengine-maven-plugin/1.3.1
mvn appengine:devserver : https://mvnrepository.com/artifact/com.google.appengine/appengine-maven-plugin/1.9.53

IAM Errors on creating, querying :
- com.google.cloud.spanner.SpannerException: PERMISSION_DENIED: io.grpc.StatusRuntimeException: PERMISSION_DENIED: Access denied. Missing IAM permission: spanner.databases.create.

  • com.google.cloud.spanner.SpannerException: PERMISSION_DENIED: io.grpc.StatusRuntimeException: PERMISSION_DENIED: Access denied. Missing IAM permission: spanner.sessions.create.

I've verified within the servlet that GOOGLE_APPLICATION_CREDENTIALS exists and is valid.
Same code works fine when using the Jetty Plugin mvn jetty:run
@jabubake jabubake added api: spanner Issues related to the Spanner API. running on app engine labels Jun 15, 2017
@jabubake
Copy link
Contributor Author

@ludoch @lesv FYI

@jabubake jabubake changed the title Authentication failures using Spanner with appengine:run locally for App Engine Standard J8 Authentication failures using Spanner with appengine:run for App Engine Standard J8 Jun 15, 2017
@garrettjonesgoogle
Copy link
Member

@jabubake is there any chance this is related to #2209 ?

@garrettjonesgoogle garrettjonesgoogle added auth type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. labels Aug 7, 2017
@lesv
Copy link
Contributor

lesv commented Sep 20, 2017

I've done this, but I may have added the IAM permission to the app engine service account. Could you retest this and we may need to document on Doug's new page.

@neozwu
Copy link
Contributor

neozwu commented Sep 21, 2017

I tested some spanner sample code on GAE 8 today and with right IAM it should work now.

@lesv lesv closed this as completed Sep 25, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lesv lesv

Labels
api: spanner Issues related to the Spanner API. auth priority: p1 Important issue which blocks shipping the next release. Will be fixed prior to next release. running on app engine type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@lesv @garrettjonesgoogle @jabubake @neozwu