Why do you need to give other coders on your app admin access to it?

Would it be feasible to just give them access to version control so they
could test locally on their machines, and then they could commit code that
is ready for testing in Appengine.. and you'd have some sort of deployment
process that pushed that code Appengine.. and they could test the app
version that was just deployed?

Seems like you'd want to keep the keys to the actual app in as few hands as
possible..

They would have to commit code to the version control.. and then get that
deployed.. before getting any sort of access to your live datastore.

Or, you could try something like this.. for coders to test a version of the
app on Appengine... they would have a testing account that they'd have to
use.. and this testing account would be associated with a testing Namespace
that didn't contain any of the sensitive datastore data you are worried
about.

Or, you could just have another separate application for testing (and only
those he need access would be able to deploy to the actual live app).. but
that seems kind of annoying.

Granted, there are always ways around these things if someone really wants
at your data.. this kind of thing just helps them stay honest.

On Fri, Sep 24, 2010 at 5:50 AM, rvjcallanan <[email protected]> wrote:

> Hi all,
>
> I have a requirement to place a thin "security" layer between the
> Datastore and my App proper. I need to be able to lock down this layer
> and prevent other coders from bypassing it and performing raw
> Datastore operations directly.
>
> I am thinking about a dual App approach where one App is a wrapper for
> its own datastore and the other App implements the main functionality
> (persisting to the Datastore of the first App via a simple API). This
> is obviously not ideal for a number of reasons which I won't go into.
>
> My question: Is there any way of achieving the same level of
> modularisation within a single App?  Python seems weak in that
> respect. I am not familiar with the Java implementation of the GAE.
> Does it fare any better? Are there any non-language mechanisms
> available to help here?
>
> Note: I don't want to get into a separate debate about trust and
> security.
>
> TIA
>
> --
> You received this message because you are subscribed to the Google Groups
> "Google App Engine" group.
> To post to this group, send email to [email protected].
> To unsubscribe from this group, send email to
> [email protected]<google-appengine%[email protected]>
> .
> For more options, visit this group at
> http://groups.google.com/group/google-appengine?hl=en.
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en.

Reply via email to