On 11 September 2010 22:36, Ben <[email protected]> wrote: > Colin, what you are describing can definitley be done in the free > version. No need to use the biz version unless you want to. I think > there is some confusion on the user authentication piece, let me try > and simplify. You have 3 options for making your application private: > 1. Write your own user management system in which your users login and > are authenticated against a "users list" you control. > 2. Use the google users service for authentication in tandem with your > own code to check against a "users list" (I would recommend this > method).
Dito - I would recommend this too :) > This means that your users would login with an existing > google account, via the App Engine Users API, but after they log in > your application would verify that paticular google username is > allowed to access your application. If they are on your list great, > if they are not you redirect them to an access denied page. > 3. Sign up for a google Apps domain and Appengine for Biz. Then the > application is restricted to the users which you have listed on your > Apps Domain. just a slight correction to that: "Sign up for a google Apps domain (and optionally Appengine for Biz) " A normal appengine app can also be restricted to a Apps Domain. http://code.google.com/appengine/kb/general.html#auth > > Hope this helps. > > -ben > > On Sep 11, 2:20 pm, colin <[email protected]> wrote: >> Thanks Barry, I had just dusted off my PHP guide, >> Do you mean my url leads to a home page with some general text and a >> logon widget that would be part of my app (programed by me), placing a >> cookie on the user's machine and restricting access to the rest of the >> site to names on a hidden list? >> If so, that would do it. >> >> On Sep 11, 8:16 pm, Barry Hunter <[email protected]> wrote: >> >> >> >> > Appengine for business - only for Apps domain users. >> >> > Normal AppEngine, - upto you to implement your own autherization >> > system. The Users API provided make it easy to autheniticate against >> > Google Accounts or Apps domains. But you are not limited to use it. >> > Can implement your own whitelist of who can login. >> >> > Sounds like your app will probably fit in the free quota that AppEngine >> > provides >> >> >http://code.google.com/appengine/docs/whatisgoogleappengine.htmlhttp:... >> >> > On 11 September 2010 18:41, colin <[email protected]> wrote: >> >> > > Thanks but I don't want a google apps domain (had to find out what it >> > > was). I am slightly confused - sorry. Here's my original post: >> >> > > Some years ago "I wrote a workflow, invoicing and payment tracking >> > > software using MS Access and VB. It gets accessed about once a day. It >> > > has about six tables and maybe 2000 records among all of them. I want >> > > to put it in a cloud and look forward to learning Python. In the >> > > future maybe three users in different citties will access the on-line >> > > version." >> >> > > I am willing to pay max $12 a year for each user if Google hosts this. >> > > Do you know of any work around? >> > > Colin >> >> > > On Sep 11, 4:19 pm, Tim Hoffman <[email protected]> wrote: >> > >> You don't need GAE4B if you want to limit logins to users of a google >> > >> apps domain, >> > >> that can be done now with normal instances. >> >> > >> T >> >> > >> On Sep 11<[email protected]> wrote: >> > >> > Oh! >> > >> > I want my app to be private. >> > >> > Looks like GAE4B. >> > >> > Can I simply add my planned (and extremely modest) app to my shared >> > >> > folder on Google Docs without GAE4B? >> > >> > Otherwise the best course would be to write a new PHP module for one >> > >> > of my Drupal sites. >> > >> > ?? >> >> > >> > On Sep 10, 8:29 pm, "Ikai L (Google)" <[email protected]> wrote: >> >> > >> > > Yes, only users on your Google Apps domain will be able to use a >> > >> > > GAE4B >> > >> > > application. You won't be able to open it up to general @gmail.com, >> > >> > > OpenID >> > >> > > users, or use your own authorization system. >> >> > >> > > On Fri, Sep 10, 2010 at 9:29 AM, colin <[email protected]> wrote: >> > >> > > > Ikai, thanks for an encouraging answer :-). >> > >> > > > The terms are more than little confusing for newbies like me and I >> > >> > > > don't want to start down a wrong track. Do I understand that my >> > >> > > > planned tool can be accessed via a url and restricted via a logon >> > >> > > > procedure to a handful of users? (like memobuild.com?) >> >> > >> > > > If my experience is positive, I want to develop bigger projects >> > >> > > > for >> > >> > > > the Google App Engine. One of these may have a smart-phone >> > >> > > > browser- >> > >> > > > interface. But first, I have to get up to speed with Python (looks >> > >> > > > good so far and I sense it will execute faster than PHP). >> >> > >> > > > On Sep 9, 8:52 pm, "Ikai L (Google)" <[email protected]> wrote: >> > >> > > > > Normal pricing. GAE4B pricing applies if you are writing an >> > >> > > > > application >> > >> > > > that >> > >> > > > > is only accessible for Google Apps (Gmail, Docs) users and not >> > >> > > > > the >> > >> > > > general >> > >> > > > > public. Here's an example: >> >> > >> > > > > Google App Engine (current) >> >> > >> > > > > You create an image sharing service anyone can use. >> >> > >> > > > > Google App Engine for Business >> >> > >> > > > > You create an expense reporting tool that you want tied to a >> > >> > > > > specific >> > >> > > > Google >> > >> > > > > Apps Domain, say, ikaicorp.com that only [email protected] can >> > >> > > > > use. >> > >> > > > This >> > >> > > > > application can be administered via the ikaicorp.com domain >> > >> > > > > console. >> >> > >> > > > > On Wed, Sep 8, 2010 at 12:15 PM, colin <[email protected]> wrote: >> > >> > > > > > I am confused by the two pricing policies (app engine for >> > >> > > > > > business and >> > >> > > > > > app engine). >> >> > >> > > > -- >> > >> > > > 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%2Bunsubscrib >> > >> > > > [email protected]> >> > >> > > > . >> > >> > > > For more options, visit this group at >> > >> > > >http://groups.google.com/group/google-appengine?hl=en. >> >> > >> > > -- >> > >> > > Ikai Lan >> > >> > > Developer Programs Engineer, Google App Engine >> > >> > > Blog:http://googleappengine.blogspot.com >> > >> > > Twitter:http://twitter.com/app_engine >> > >> > > Reddit:http://www.reddit.com/r/appengine >> >> > > -- >> > > 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 >> > > athttp://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. > > -- 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.
