Received: by 10.66.79.233 with SMTP id m9mr2975051pax.37.1350327030525;
        Mon, 15 Oct 2012 11:50:30 -0700 (PDT)
X-BeenThere: gtm-oauth2@googlegroups.com
Received: by 10.68.141.133 with SMTP id ro5ls19855429pbb.1.gmail; Mon, 15 Oct
 2012 11:50:30 -0700 (PDT)
Received: by 10.66.77.131 with SMTP id s3mr3374002paw.24.1350327030211;
        Mon, 15 Oct 2012 11:50:30 -0700 (PDT)
Received: by 10.66.77.131 with SMTP id s3mr3374001paw.24.1350327030195;
        Mon, 15 Oct 2012 11:50:30 -0700 (PDT)
Return-Path: <grobb...@google.com>
Received: from mail-pa0-f51.google.com (mail-pa0-f51.google.com [209.85.220.51])
        by gmr-mx.google.com with ESMTPS id js4si4079542pbb.2.2012.10.15.11.50.30
        (version=TLSv1/SSLv3 cipher=OTHER);
        Mon, 15 Oct 2012 11:50:30 -0700 (PDT)
Received-SPF: pass (google.com: domain of grobb...@google.com designates 209.85.220.51 as permitted sender) client-ip=209.85.220.51;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of grobb...@google.com designates 209.85.220.51 as permitted sender) smtp.mail=grobb...@google.com; dkim=pass header...@google.com
Received: by mail-pa0-f51.google.com with SMTP id kq12so4497442pab.10
        for <gtm-oauth2@googlegroups.com>; Mon, 15 Oct 2012 11:50:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=google.com; s=20120113;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:x-system-of-record;
        bh=2DhMi+hUgfR+wI+HeeEWdrUAfC7w1DZBe0Nf74UZoxM=;
        b=A4OIHoeRFi28Gh1rBco98XbXL4Wfx9TXbP9z9Gha4VwD+jqQvuJjsHQ5wSaOEbP3qs
         u7wuVdKlWu7jKR9Cef1GyF5wqARfO2A8JwmaKkBk4sE4JBFQbjJ7X9L5afHxqBfunxM1
         N8Arn5zQHdMelsrW0lSNk0/OlKQSLpqszJ7Wc741y3/El5YPK7AfkvS5FE44RtbZCM7L
         3DKSNNauR81+kw16RWSUetMKGHi0D2UI7BCaJ4kA7jx7k2y3vyKTy4GTnw8UH9dyfldO
         oLnTdKN0OLMJ90p4LTcADyry8j2DuRBxitL4cdJmzwDiPcnIJReUuhfybh3qDY8jq135
         1i7w==
        d=google.com; s=20120113;
        h=mime-version:in-reply-to:references:from:date:message-id:subject:to
         :content-type:x-system-of-record:x-gm-message-state;
        bh=2DhMi+hUgfR+wI+HeeEWdrUAfC7w1DZBe0Nf74UZoxM=;
        b=bfKtYWKaOVR1neOcXke83bMipPK1n0ZMp+Vkn1xabgvSBo9SGsZ12yJrsxQ9eCLqmu
         hk9QmIeUSmcHyAmFaTEvg//SiLrAd9ROAARP4nszE76Fgn7gmpEVzISDHkHStu7iWNDi
         u5Gl3/Cm7KqoqazRWh4GCIdPYt6StL0gcf3AA2PuM9Hk00tB0IEdvSR/kKCE+eMeWkjf
         RCNZVeUFO74nBq1oKm5i/3jm/1NtGhVRov/z7f9Rm38DpfGIgursNU4sN85cjcET+aeu
         7ndZzF6+KDyeOASbbZaNdCEYJ4nVU+cMuC4K2krZ3kb9TPT5Sa9emBt42bVDOyJBQ4n6
         fF1g==
Received: by 10.68.224.161 with SMTP id rd1mr40526395pbc.49.1350327029998;
 Mon, 15 Oct 2012 11:50:29 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.68.221.106 with HTTP; Mon, 15 Oct 2012 11:49:59 -0700 (PDT)
In-Reply-To: <4632b32f-f102-4edf-9a18-f7321c02b4ec@googlegroups.com>
References: <4632b32f-f102-4edf-9a18-f7321c02b4ec@googlegroups.com>
From: Greg Robbins <grobb...@google.com>
Date: Mon, 15 Oct 2012 11:49:59 -0700
Message-ID: <CANZFoDZAz4_AUsebzA8tdy7jnSGgNN6ZGgmr-tkWrHZ95C-...@mail.gmail.com>
Subject: Re: Exchanging Access Code for Access Token
To: gtm-oauth2@googlegroups.com
Content-Type: multipart/alternative; boundary=e89a8ff24ff6f422e404cc1d8237
X-System-Of-Record: true
X-Gm-Message-State: ALoCoQmPVaOlwV8Asf7rQF3L1UTxwTGpKSAjRyVNy/dq7EtTs+sDpx5+zudNvT0c0c9xTvzdM+U2pCeVjbYwr5X+YjZDAlx7UPI1YMdOGlQGYuk8UkroZUg3HzF0KX+F6DQy0ZUrzUljfJMeeV7gqA2xufhEhbMdk5b6IKyEt3d8OPOenJZS8Mb9upGuhwalFn8dZWskfw0Pxoi6ZMfR8N8ZosznC8uANQ==

--e89a8ff24ff6f422e404cc1d8237
Content-Type: text/plain; charset=ISO-8859-1

The GTM OAuth 2 library does the exchange of a refresh token for an access
token automatically. It can add the access token to the headers of an
NSMutableURLRequest for use with NSURLConnection, or can be used to
authorize requests made with the GTM HTTP Fetcher class.

Details are at
http://code.google.com/p/gtm-oauth2/wiki/Introduction#Using_the_Authentication_Tokens

--e89a8ff24ff6f422e404cc1d8237
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

The GTM OAuth 2 library does the exchange of a refresh token for an access =
token automatically. It can add the access token to the headers of an NSMut=
ableURLRequest for use with NSURLConnection, or can be used to authorize re=
quests made with the GTM HTTP Fetcher class.<div>

<br></div><div>Details are at <a href=3D"http://code.google.com/p/gtm-oauth=
2/wiki/Introduction#Using_the_Authentication_Tokens">http://code.google.com=
/p/gtm-oauth2/wiki/Introduction#Using_the_Authentication_Tokens</a></div>

<div><br></div>

--e89a8ff24ff6f422e404cc1d8237--