google-cloud-endpoints

Can someone specify (with some sample code) how to verify the firebase token in an google cloud endpoint? The recently asked question does not clarifiy it at all ( How to integrate firebase authentication with google app engine endpoints ) Google Authentication in endpoint is done automatically by adding the User Parameter to an endpoint. Facebook Tokens can be verified in an cloud endpoint with the facebook graph api like this: @ApiMethod(name = "endpoint.addUser", httpMethod = HttpMethod.POST) public ResultObject addUser(HttpServletRequest request, User pUser) throws OAuthRequestException {

I am using appengine cloud endpoints and objectify. I have previously deployed these endpoints before and now I am updating them and it is not working with Objectify. I have moved to a new machine and running latest appengine 1.8.6. Have tried putting objectify in the classpath and that did not work. I know this can work, what am I missing?? When running endpoints.sh: Error: Parameterized type com.googlecode.objectify.Key<MyClass> not supported. UPDATE: I went back to my old computer and ran endpoints.sh on same endpoint and it worked fine. Old machine has 1.8.3. I am using objectify 3.1.

I am implementing Cloud Endpoints with a Python app that uses custom authentication ( GAE Sessions ) instead of Google Accounts. I need to authenticate the requests coming from the Javascript client, so I would like to have access to the cookie information. Reading this other question leads me to believe that it is possible, but perhaps not documented. I'm not familiar with the Java side of App Engine, so I'm not quite sure how to translate that snippet into Python. Here is an example of one of my methods: class EndpointsAPI(remote.Service): @endpoints.method(Query_In, Donations_Out, path='get

A few days ago I've started developing a Backend for Mobile Applications using Google App Engine and Google Cloud Endpoints . This tutorial shows how the endpoints are getting generated automatically, as well as the client library for Android. So we have our Entity: @Entity public class Person implements IsSerializable{ @Id @GeneratedValue(strategy = GenerationType.IDENTITY) private Key key; private String name; //... } And the endpoint for this class: @Api(name = "personendpoint") public class PersonEndpoint { @ApiMethod(name = "getPerson") public Person getPerson(@Named("id") Long id) { ...

I am trying to decide which option to go with. (or another if it is better) This is for a messaging type app where there will be high volume of notifications and database writes. Option 1 - Google App Engine using Cloud Endpoints and Cloud Datastore Pros: Able to build out an API the way I would like. Scalable Cons: More work implementing a notification system. (Which will end up being Firebase Cloud Messaging) Option 2 - Firebase Pros: Able to use the Firebase Database, Firebase User Authentication, Firebase Cloud Messaging(notifications) Detailed use statistics for all devices Cons: No API

My iOS app uses a Java-based server and communicates with it using Google Cloud Endpoints. Normally the server listens on https://myservice.appspot.com/_ah/api/rpc . How can I debug my server code? After I run it with Debug As | Web Application inside Eclipse and change its URL to https://localhost:8888/_ah/api/rpc the client cannot connect. I don't think it's a firewall issue because URLs with localhost:8888 work for other client-server pairs. So does one need to take any special steps for debugging code in Google Web Application projects with Google Cloud Endpoints in Eclipse, and is there a

I am trying to deploy my react express app on google app engine. Everything works fine on localhost but when I deploy I get a 404 error: I assume this could be something wrong with my handlers but i'm not to sure, help would be much appreciated. Cannot GET / Failed to load resource: the server responded with a status of 404 () This is what the console log says: httpRequest: { latency: "0.006s" referer: "-" remoteIp: "2001:8000:11d3:ed00:4854:5aba:9f93:dd47" requestMethod: "GET" requestUrl: "/" responseSize: "139" status: 404 userAgent: "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_2)