4 messages in com.googlegroups.google-mashup-editorRe: Implenentation of authentication
FromSent OnAttachments
corporaterat20 Jun 2007 05:10 
Jason20 Jun 2007 10:46 
levik26 Jun 2007 08:04 
corporaterat26 Jun 2007 09:12 
Subject:Re: Implenentation of authentication
From:corporaterat (arju@gmail.com)
Date:06/26/2007 09:12:17 AM
List:com.googlegroups.google-mashup-editor

Yes, this is how I have implemented it for now. It is twisted, but at least it works till GME provides a cleaner approach. I published the code at http://dynamicauth.googlemashups.com/ - incase anyone wants to see how it works.

regds arjun

On Jun 26, 11:04 am, levik <levi@gmail.com> wrote:

One thing to note is that you can currently have different pages in your app, some of which require authentication and some do not (you can provide a "public" landing page that links to "authentication required" pages that contain edit functionality. The user would only be prompted to log in when going to a protected page for the first time.

On Jun 20, 8:10 am, corporaterat <arju@gmail.com> wrote:

Hello, I'd like to bring up the concept of authentication in GME

as it stands today, it looks like one can only decide statically whether the app should be 'authenticate=true' or 'false'.

I think this should be dynamic in nature, or, controls that need authentication should prompt for authentication when activated.

Consider for example, the TaskList example. If I change it to authenticate=false, then the edit button disappears.

Apparently, to edit data, GME requires a user to be logged in. I think this should be up to the application developer. Furthermore, there should be an option to do dynamic authentication. In the current mechanism, if I write an app with auth=true, one needs to log in otherwise the app is not visible. This is a problem for viewers who do not have a google acct (nor do they want to sign up for one).- Hide quoted text
-

- Show quoted text -