Difference between revisions of "Oauth2"
m (improve layout)
m (Added section on OAuth2-related account settings in Claws. Revised trouble-shooting tip about dismissing Google's warning about giving Claws access to a Gmail account.)
|Line 1:||Line 1:|
=== Setting up OAuth 2.0 for Gmail ===
=== Setting up OAuth 2.0 for Gmail ===
|Line 59:||Line 70:|
It's possible / probable that Gmail will 'complain' about giving access to an unverified third-party app. If this keeps you from using Claws to access your Gmail, you may need to
It's possible / probable that Gmail will 'complain' about giving access to an unverified third-party app. If this keeps you from using Claws to access your Gmail, you may need to to Gmail's and your security settings thereto access to .
Revision as of 13:23, 26 March 2022
Claws Mail Account Settings for OAuth 2.0
When setting up an account with OAuth2, besides correctly filling out the 'OAuth2' page, you also need to make sure you have the correct settings on the 'Receive' and 'Send' pages:
'Receive' page (POP): Authenticate before POP connection: Authentication method = 'OAuth2'. 'Receive' page (IMAP): Authentication method = 'OAuth2'. 'Send' page (POP / IMAP): SMTP Authentication: Authentication method = 'OAuth2'.
Setting up OAuth 2.0 for Gmail
Follow the instructions here: https://support.google.com/googleapi/answer/6158849
Note: Before starting, make sure that you are not logged in (via webmail) to any Gmail account, or that you are logged in to only the relevant account.
When setting up the project use these settings:
Project name: Anything of your choice Publishing status (of project): 'Testing' (initial default) User type: External
Notes related to the above:
1. If/when you create a new project, if it appears that the process has stalled, look in the top-right corner for a notification icon that you can click on and then select the relevant project. This should then open that project's dashboard so you can continue with the process. (As of 24 Mar 2022.)
2. Regarding Google's above-linked instructions related to the "Credentials" page: Where it says "Click 'New Credentials'" it should read "Click '+ CREATE CREDENTIALS'" (as of 24 Mar 2022).
3. Regarding "Publishing status", there isn't an option to choose this when you are creating a new project. It seems that the status will be considered as 'Testing' unless/until you have clicked on 'Publish App' in the 'Publishing status' section of the 'OAuth Consent Screen'; then it will be considered as being 'In Production'. (However, 'publishing' the app may require that it be submitted to Google for verification, which requires a variety of submissions that seem more relevant to the developers of an app for 'everyone' rather than for a user who is trying to set something up for themselves.) It is possible to get it working by using the 'Testing' status if you add the relevant email address to the 'Test Users' list on the 'Edit App Registration' - 'Test Users' page of the 'OAuth Consent Screen' setup process (or on the main 'OAuth Consent Screen' page). However, authorization with this status may only last for seven days. (As of 24 Mar 2022.)
OAuth consent screen settings:
App name: Anything of your choice User support email: Your own email Developer email: Your own email App domain entries: Leave blank
Click on 'Add or Remove Scopes'. Select (check the box) this entry: "Gmail API, https://mail.google.com/, Read, compose, send and permanently delete all your email from Gmail" (Note that the list is in alphabetical order and you may need to go to a later page to find this entry. Also, if you can't find it in the list, you can enter the URL manually at the bottom of the page to add it to the list.) Click on 'Update'. Confirm that the section 'Your restricted scopes' shows the entry you just added. Click on 'Save and Continue'.
Getting the ClientID
APIs and Services on the left menu, then Credentials entry Copy the ClientID to the custom entry box on Claws Mail Oauth2 account preferences screen. Select "Edit Oauth Credentials" (pencil icon), then copy the Client Secret to the entry in Claws Mail Oauth2 account preferences screen.
It's possible / probable that Gmail will 'complain' about giving access to an unverified third-party app. If this keeps you from using Claws to access your Gmail, you may need to log in to Gmail's web-mail interface and review / revise your security settings there. This may involve dismissing the warning Google gives about the Project that you set up for Claws to access GMail on your account. If you dismiss a Warning, Google may then ask you why you are dismissing it, providing several options, leaving you free to choose the one which seems most suitable.
Setting up OAuth 2.0 for Microsoft - for Outlook or Exchange
Sign in to microsoft account
Go to Azure Active Directory > App registrations
Choose "New Registration"
Display name: Anything you choose Application (client) ID - will be auto generated Object ID - will be auto generated Directory (tenant) ID - will be auto generated Supported account types - set to "All Microsoft account users"
Once app is registered you can configure it:
Branding tab - any entries you like
Authentication tab -
Redirect URI: https://login.microsoftonline.com/common/oauth2/nativeclient Supported account types: "Accounts in any organizational directory (Any Azure AD directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)"
Certificates & secrets tab - No entries needed
Token configuration - No entries needed
API permissions tab - Add these:
- IMAP.AccessAsUser.All - Mail.ReadWrite - Mail.Send - offline_access - POP.AccessAsUser.All - SMTP.Send
Expose an API tab - No entries needed
Owners tab - No entries needed
Manifest tab - Leave at defaults
Quickstart tab - Leave alone
Integration assistant - Leave alone
Once configured the ClientID (also called Application ID) can be copied over to Claws Mail custom ClientID box. No Client Secret is needed - leave that entry blank in Claws Mail's custom Client Secret box.