Best practices to authenticate requests comming from my AppEngine app

69 views
Skip to first unread message

Ronoaldo José de Lana Pereira

unread,
Mar 19, 2012, 4:32:47 PM3/19/12
to google-a...@googlegroups.com
We're integrating our AppEngine app with third parties services. They need to restrict access on the resources that we are using. They requested an IP address to open their firewall rules, which is not a good practice, since all appengine apps may share one or more ip addresses to perform URLFetch requests. How should we do this access control securely? Is there any secure way to be sure that the HTTP request is comming from my application and not from an untrusted source?

Any tips are welcome.

Best Regards,

-Ronoaldo

Brandon Wirtz

unread,
Mar 19, 2012, 4:37:39 PM3/19/12
to google-a...@googlegroups.com

Get a dream host account. Call it, have it call your third party. That way only 1 IP.

 

 

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/nDzt2E5BuHkJ.
To post to this group, send email to google-a...@googlegroups.com.
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.

Ronoaldo José de Lana Pereira

unread,
Mar 20, 2012, 11:03:51 AM3/20/12
to google-a...@googlegroups.com
Thanks for your reply Brandon. We are doing this currently, but this adds some small network overhead. We are not using Dreamhost, we have a VPS here in our country, with an Apache mod_proxy server to route the requests to the destination. Good to know from experts that this is a good way to solve the problem, I'll checkout Dreamhost plans anyway.

Best Regards,

-Ronoaldo


Em segunda-feira, 19 de março de 2012 17h37min39s UTC-3, Brandon Wirtz escreveu:

Get a dream host account. Call it, have it call your third party. That way only 1 IP.

 

 

From: google-appengine@googlegroups.com [mailto:google-appengine@googlegroups.com] On Behalf Of Ronoaldo José de Lana Pereira
Sent: Monday, March 19, 2012 1:33 PM
To: google-appengine@googlegroups.com
Subject: [google-appengine] Best practices to authenticate requests comming from my AppEngine app

 

We're integrating our AppEngine app with third parties services. They need to restrict access on the resources that we are using. They requested an IP address to open their firewall rules, which is not a good practice, since all appengine apps may share one or more ip addresses to perform URLFetch requests. How should we do this access control securely? Is there any secure way to be sure that the HTTP request is comming from my application and not from an untrusted source?

 

Any tips are welcome.

 

Best Regards,

 

-Ronoaldo

--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/nDzt2E5BuHkJ.

To post to this group, send email to google-appengine@googlegroups.com.
To unsubscribe from this group, send email to google-appengine+unsubscribe@googlegroups.com.

Jeff Dutton

unread,
Mar 23, 2012, 2:28:34 PM3/23/12
to google-a...@googlegroups.com
Ronoaldo,

Assuming you are using HTTPS, what about using a shared secret either as a query parameter in the URLs or as a header in the HTTP request?  That is effectively what Google Cloud Storage uses to authenticate access to storage.

Good luck,
Jeff Dutton
Reply all
Reply to author
Forward
0 new messages