You'll need to partition the data at the application level. We don't provide global ACLs for the datastore. You may be able to use Entity Groups for a lightweight version of this, but ultimately it'll be up to your application to decide who has the rights to see which data.
On Sat, Dec 5, 2009 at 8:47 AM, VSS <[email protected]> wrote: > Any updates on my previous question ? > > Thank you!! > VSS > > On Dec 4, 4:44 pm, VSS <[email protected]> wrote: > > We are creating an Active Directory Kind of an application on App > > Engine. What I want to know is there a way to store data securely so > > that I can sell this application as a service to other domains. I > > should not be able to acess data produced by users of other domains. > > > > I noticed if we use JDO, I can view the information. Is there a work > > around so that data can be viewed only by authorized people and not > > even the creators of the application? or do we have to implement our > > own encryption and decryption authorization processes. > > -- > > You received this message because you are subscribed to the Google Groups > "Google App Engine for Java" group. > To post to this group, send email to > [email protected]. > To unsubscribe from this group, send email to > [email protected]<google-appengine-java%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine-java?hl=en. > > > -- Ikai Lan Developer Programs Engineer, Google App Engine -- You received this message because you are subscribed to the Google Groups "Google App Engine for Java" 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-java?hl=en.
