[Users] OAuth2 refresh token not obtained

[Dustin Miller]

On Tue, 10 May 2022 21:11:46 -0700
Geoffrey Leach <geoffleach.gl at gmail.com> wrote:

> o Two accounts, two laptops, 2 users. 
> 
DM: Okay, the thing to watch for here is to make sure that the account
you are getting the authorization code for from Google via your web
browser is the same account whose settings you are pasting the code
into in Claws.

DM: Am I right in assuming that the account you are working with is
using the publishing status of 'Testing' in the API console?
> 
> o What I normally do is just to punch the Authorize button on the
> OAuth2 page.
> 
DM: From what I understand of the process, this should never work if
you are using an account with 'Testing' status and the authorization
code has expired, since only doing that would mean you were still using
the old authorization code.
> 
> When that did not work, I re-requested an authorization code, which
> worked (new code) but Authorize did not work. I then went back to the
> API Console and verified that nothing has changed.
> 
DM: Is this based on your memory of what you did before, or did you
actually go through the process again and record each step? Here is the
process that worked for me:

* 1. On the Claws OAuth2 page, click on the 'Open default browser with
  request' button. (This will take you to your browser. Make sure you
  sign in to the correct Gmail account.)

* 2. Assuming you've clicked through whatever screens you've needed to
  and no errors have shown up in your browser, you should eventually
  see a screen that gives you an authorization code to use.

* 3. Copy this code from the browser screen to the Claws OAuth2 page's
  'Authorization code' field. (Note that this needs to completely
  replace the old code.)

* 4. Click on 'Authorize', then on 'OK' and 'Close' to complete the
  process and exit the account settings. (If you want to make sure that
  clicking the 'Authorize' button is doing what it's supposed to, then
  first go to both the 'Basic' and 'Send' pages and completely clear
  the contents of the 'Password' fields. After you've clicked
  'Authorize', you can check these pages again and the 'Password'
  fields should have been automatically filled again. This normally
  isn't necessary to do, but can be helpful if you want to make sure
  that you actually activated the 'Authorize' button when you tried to
  click it.)

DM: My understanding is that the above process should work, assuming
you were successfully using OAuth2 before and you haven't changed any
settings anywhere, unless of course something changed on Google's end.

DM: When you do try this again, I would strongly recommend that you
take 'very detailed' notes in regards to each step that you do. If it
works, great -- you can then keep the notes on hand for future
reference, as needed. If it doesn't work, then you can post those notes
here, in case I or others can use them to give you more ideas of what
to try. Would probably also be helpful to provide copy/paste or
word-for-word quotes of any relevant error messages. Hope that helps,
---Dustin
> 
> On Wed, 11 May 2022 06:51:20 +0600
> Dustin Miller <dustbiz at gmail.com> wrote:
> 
> > On Tue, 10 May 2022 13:32:23 -0700
> > Geoffrey Leach <geoffleach.gl at gmail.com> wrote:
> >   
> > > Performing the weekly re-authorization for the Google account,
> > > Google does not give authorization. 
> > >     
> > DM: Hi, Geoffrey. Presumably this is with a Gmail account that was
> > working with OAuth2 previously and you haven't changed anything in
> > Claws since then? Please mention whether either of these two
> > assumptions is incorrect.
> > 
> > DM: Do you use more than one Gmail account? If so, have you
> > double-checked that, when you go to your web browser to get the
> > authorization code you need, you are signed / signing in to the
> > correct account?
> > 
> > DM: Could you work through the process again of trying to do the
> > authorization, and post here the detailed steps of what you did?
> > This could help to determine if there is a problem in your process.
> > If there are any areas of the process you are unsure of, you can
> > refer to the FAQ page here:
> > https://www.claws-mail.org/faq/index.php/Oauth2 . ---Dustin  
> > > 
> > > Details on the API Dashboard have not changed. CM version 4.1.0
> > >  
> > _______________________________________________
> > Users mailing list
> > Users at lists.claws-mail.org
> > https://lists.claws-mail.org/cgi-bin/mailman/listinfo/users  
> 
> _______________________________________________
> Users mailing list
> Users at lists.claws-mail.org
> https://lists.claws-mail.org/cgi-bin/mailman/listinfo/users