                                                                                                                                                                                                                                                                
Received-SPF: neutral (google.com: 64.13.232.40 is neither permitted nor denied by best guess record for domain of li...@lobaugh.net) client-ip=64.13.232.40;
Message-ID: <4F7884A5.2080506@lobaugh.net>
Date: Sun, 01 Apr 2012 09:39:01 -0700
From: Ben Lobaugh <li...@lobaugh.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20120327 Thunderbird/11.0.1
MIME-Version: 1.0
To: meetup-api@googlegroups.com
Subject: Re: [meetup-api] Problems with OAuth2 Flow
References: <9d46104d-0a71-4655-95ca-5e620ea5bfdb@jx17g2000pbb.googlegroups.com>
In-Reply-To: <9d46104d-0a71-4655-95ca-5e620ea5bfdb@jx17g2000pbb.googlegroups.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Rahul,

If your app has already been authenticated by the user then they know 
that Meetup is providing the auth. In that case it should be fine to 
simply have them logged in. Until they revoke your apps access you 
should be good to go.

Ben

On 4/1/12 12:17 AM, Rahul wrote:
> Hi,
>
> I'm new to the OAuth2 flow. Here is a basic problem:
>
> - When a new user grants permissions to my application, I want to
> inform him that he would be redirected to meetup website.
>
> - If the user has already authenticated my application, he never sees
> the meetup authenticate page. He gets redirected back to my
> application.
>
> In the second scenario, it makes no sense to display the additional
> notice that the user would be transfered to meetup authentication
> page.
>
> How do you handle it?
>
>
> Rahul
>