tag:blogger.com,1999:blog-3895474834344383709.post2600296062011085036..comments2011-04-09T01:06:30.835-07:00Genehttp://www.blogger.com/profile/17596228613938166964noreply@blogger.comBlogger7125tag:blogger.com,1999:blog-3895474834344383709.post-41659280795655463502011-04-09T01:06:30.835-07:002011-04-09T01:06:30.835-07:00How would integrate with a GWT app as opposed to GAE or servlet-GETSimple Guyhttp://www.blogger.com/profile/18347101359402080251noreply@blogger.comtag:blogger.com,1999:blog-3895474834344383709.post-83920937279305705202011-01-26T12:27:50.069-08:002011-01-26T12:27:50.069-08:00Gene<br />Did you encounter any errors with guice provisioning while running the sample app? <br />I&#39;m getting errors on the app engine - mentioned the details here<br />http://www.google.com/support/forum/p/apps-apis/thread?tid=09cc128445f7d43d&amp;hl=enJaspalhttp://www.blogger.com/profile/10390829886552125278noreply@blogger.comtag:blogger.com,1999:blog-3895474834344383709.post-36471460265833995502011-01-25T12:09:02.169-08:002011-01-25T12:09:02.169-08:00I think in most instances the Single Sign on functionality will be required, and it is up to you to implement it on your site, so if you don&#39;t require it, don&#39;t implement the sign on code at your end.<br /><br />For example. Google redirects you to a specific login URL which you specify in the manifest. [S} You then authenticate that user in the back end with Google&#39;s servers, then you might create a session object setting the application up as being logged in for that particular user. If you don&#39;t require any login functionality. Simply skip the part after [S}.Genehttp://www.blogger.com/profile/17596228613938166964noreply@blogger.comtag:blogger.com,1999:blog-3895474834344383709.post-56388428969814001932011-01-25T12:02:47.615-08:002011-01-25T12:02:47.615-08:00Hey Gene<br />Thanks for the quick response. <br />Have another question <br />1. Why is the single sign on required even when the hello world app does not need it? Is it just a mandatory requirement which google has assuming more real world app will have a sign in functionality<br /><br />Thanks a lot man. Solved a lot of confusion for meJaspalhttp://www.blogger.com/profile/10390829886552125278noreply@blogger.comtag:blogger.com,1999:blog-3895474834344383709.post-85454000683445521482011-01-25T11:42:56.154-08:002011-01-25T11:42:56.154-08:001. Correct.<br />2. Correct.<br />3. Correct.Genehttp://www.blogger.com/profile/17596228613938166964noreply@blogger.comtag:blogger.com,1999:blog-3895474834344383709.post-655436428245503552011-01-25T11:32:02.595-08:002011-01-25T11:32:02.595-08:00Hey there<br />I&#39;m very new to the whole google app, marketplace ecosystem. Wanted to confirm my understanding.<br /><br />1. I have a sample app deployed to Google App Engine (GAE) lets call this app &#39;MyHelloWorld&#39;. This app can be accessed on the appspot.com url without needing any login<br />2. I want to be able to add this app i.e. &#39;MyHelloWorld&#39; to the Google app Marketplace (GAM) so that all the users on my domain can access the &#39;MyHelloWorld&#39; app from the top nav.<br /><br />Stuff which I&#39;m not sure about<br />1. The sample code for single-sign on given on the GAM needs to be integrated with the &#39;MyHelloWorld&#39; App - right?<br />2. The manifest entry in the listing created on GAM is used to identify the appropriate app.<br />3. Once the setup has been done the users in my domain will be able to access the &#39;MyHelloWorld&#39; app from the top navJaspalhttp://www.blogger.com/profile/10390829886552125278noreply@blogger.comtag:blogger.com,1999:blog-3895474834344383709.post-10887690814584655902010-11-06T00:45:13.649-07:002010-11-06T00:45:13.649-07:00Great article, thanks a lot! This is exactly what I&#39;m searching for ;)Marco Sindonihttp://www.blogger.com/profile/02720511448473115951noreply@blogger.com