Hi Guys, While there seems to be this related thread on the forum Ikai Lan has mentioned, which you may follow / add to the thread as need be.. http://www.google.com/support/forum/p/apps-apis/thread?tid=52e36f012c2436c3&hl=en
..I think our options for the moment are pretty clear. For developers over Google App Engine, I think the current option is to support OpenID and then list yourself in the Google Marketplace. Nicholas Johnson's AEoid <http://github.com/Arachnid/aeoid> seems to be a good place to start. You may want to check out Evan Kaufman's fork<http://github.com/EvanK/aeoid>which include many useful changes and Scott Ellis' fork <http://github.com/sje397> which include Evan's changes and a little more (in contains some of his specific code too, which you might want to update). I tested Scott's fork and it seems to work fine in my development environment. But, my concern is should this not be part of Google App Engine itself ? In could be better if OpenID support was by default available (may be as a deployment option) in Google App Engine, instead of each one of us having to integrate a package which we think is good and that which also includes session maintenance. Once this OpenID support is included in default Google App Engine, it is easier for existing apps to adapt to the authentication mode and then list themselves in the marketplace. So, this is for App Engine guys at Google to decide. Another way in which App Engine people at Google can help is to provide a "click to install" option. This will require very minimal changes to the existing apps. In this approach applications can be marked for sale - may be from the apps dashboard by the developer, and can redeployed to a customer's App Engine account, after the customer has paid for the same via Google. Of course, such redeployed apps cannot be resold, from that apps dashboard. Google can take a cut from the recurring/one-time sale proceedings and also by enabling billing for those customers. Come on App Engine guys, help us and help yourself make some money. We are already betting on you. Thanks & Regards, R.Rajkumar On Fri, Mar 12, 2010 at 12:25 AM, Ikai L (Google) <[email protected]> wrote: > Can you guys also ask here? > > http://www.google.com/support/forum/p/apps-apis?hl=en > > I apologize if it seems like I'm punting the question a bit, but this > really isn't a subject I have much familiarity with. Trying to keep up > with all the different Google APIs is more than a full-time job in and > of itself =). > > On Thu, Mar 11, 2010 at 9:42 AM, Jérémy Selier <[email protected]> > wrote: > > I'm interested too. I've tried using with > http://openid-consumer.appspot.com/ > > and https://www.google.com/accounts/o8/site-xrds?hd=mydomain.com and > > this seems to not working. > > I think that we have to use some custom version of the openid consumer > > lib to be able to deal with OpenID Google Apps discovery. > > > > -- > > Jeremy > > > > On Mar 11, 3:51 pm, Wooble <[email protected]> wrote: > >> You can only have your app authenticate to a single apps domain, and > >> you have to choose that domain when you create the application. This > >> makes it kind of impossible to sell integration to a google apps > >> domain you weren't aware of when you wrote the app, let alone 2 or > >> more of them. > >> > >> On Mar 11, 7:08 am, Tim Hoffman <[email protected]> wrote: > >> > >> > >> > >> > Hi > >> > >> > I don't think you would need it. An app engine app can already use > >> > the apps domain to authenticate. > >> > That page you are referring to is for applications not running in app > >> > engine (say on ec2, that want to use the users google apps account to > >> > login to that third party service). > >> > >> > By the way there are a few libraries out there for python. > >> > >> > T > >> > >> > On Mar 11, 10:52 am, molicule <[email protected]> wrote: > >> > >> > > Hi, > >> > > The sso page here does not have any python openid libraries for the > >> > > marketplace??http://code.google.com/googleapps/marketplace/sso.html > >> > >> > > Is that an oversigght? is there any way a python google appengine > app > >> > > can > >> > > participate in the marketplace?? > >> > >> > > Thanks > >> > > S. Sriram > >> > >> > > On Mar 10, 9:56 am, Roberto Saccon <[email protected]> wrote: > >> > >> > > > I am planning to integrate an appengine hosted app on custom > domain > >> > > > with the Apps Marketplace. Has anybody done that yet and has > >> > > > experiences to share ? > >> > >> > > > One thing I am wondering about is whether the customer has to add > on > >> > > > his Google Apps Admin Panel both, the Market place and the > appengine > >> > > > app (and perform there optionally the domain-mapping), or if it > could > >> > > > be handled all by just adding the Marketplace app. > >> > >> > > > -- > >> > > > Roberto > > > > -- > > 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. > > > > > > > > -- > Ikai Lan > Developer Programs Engineer, Google App Engine > http://googleappengine.blogspot.com | http://twitter.com/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%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/google-appengine?hl=en. > > -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ http://crm.ifreetools.com -- 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.
