HTTP/1.1 200 OKCache-Control: no-cache, no-store, max-age=0, must-revalidatePragma: no-cacheExpires: Fri, 01 Jan 1990 00:00:00 GMTDate: Wed, 28 Dec 2011 10:07:21 GMTContent-Type: application/jsonX-Content-Type-Options: nosniffX-Frame-Options: SAMEORIGINX-XSS-Protection: 1; mode=blockServer: GSETransfer-Encoding: chunked{"access_token" : "1.AH0000cuXMQmlcncZleg","token_type" : "Bearer","expires_in" : 3600,"id_token" : "token.eyJpZt9pIhIy-EpnNltq7_Q"}
Even with access_type=offline if there was a refresh token already
issued for the same user, scopes and client then auto-approval will
kick in and no new refresh token will be issued. Since one was issued
already there is no reason you should go through this flow again.
At this point you are either not using the proper flow or you lost the
original refresh token.
If you really want a new refresh token, even though you were already
given one, then also add approval_prompt=force to the auth request.
That will prevent auto-approval from happening.
Marius