31,028
edits
Module OAuth: Difference between revisions
Jump to navigation
Jump to search
m
→Setup
Tag: 2017 source edit |
m (→Setup) Tag: 2017 source edit |
||
| Line 44: | Line 44: | ||
====For Microsoft Office365==== | ====For Microsoft Office365==== | ||
Client ID / Secret ID: See chapter | Client ID / Secret ID: See chapter [How to get my Client / Secret ID]. | ||
Tenant: The ID of the tenant provided by Microsoft. Example: 123456ab-1234-5678-abdc-12345678abcd | Tenant: The ID of the tenant provided by Microsoft. Example: 123456ab-1234-5678-abdc-12345678abcd | ||
| Line 57: | Line 57: | ||
====For Google==== | ====For Google==== | ||
Client ID / Secret ID: See chapter | Client ID / Secret ID: See chapter [How to get my Client / Secret ID]. | ||
Scope: Choose the scope '''gmail_full''' | Scope: Choose the scope '''gmail_full''' | ||
| Line 87: | Line 87: | ||
Not yet available ! Will probably be ... | Not yet available ! Will probably be ... | ||
Client ID / Secret ID: See chapter | Client ID / Secret ID: See chapter [How to get my Client / Secret ID]. | ||
Tenant: The ID of the tenant provided by Microsoft. Example: 123456ab-1234-5678-abdc-12345678abcd | Tenant: The ID of the tenant provided by Microsoft. Example: 123456ab-1234-5678-abdc-12345678abcd | ||
| Line 103: | Line 103: | ||
* For Google, when your oauth entry is published in Production, Google verified, refresh_token expire is 180 days and has unlimited access_token refreshes. | * For Google, when your oauth entry is published in Production, Google verified, refresh_token expire is 180 days and has unlimited access_token refreshes. | ||
== | == See chapter [How to get my Client / Secret ID] == | ||
To create an OAuth entry, you need a Client and Secret ID (an sometimes a Tenant ID). Getting them depends on your OAUTH provider. | |||
=== For Microsoft 365=== | |||
The following steps are: | |||
A thread in forum is also available related to use of OAuth2 for SMTP and IMAP: https://www.dolibarr.org/forum/t/oauth-office-365-and-email-collector/23437 | * Go on https://portal.azure.com - Manage application to create an Application | ||
* Then set property "Assignation required to No (not sure this is necessary) | |||
* Then set Authorized API | |||
* Then set Authentification chapter | |||
* Then set Certificate & Secret | |||
The is some documentation here: | |||
* See https://afterlogic.com/mailbee-net/docs/OAuth2Office365NonInteractive.html and https://learn.microsoft.com/fr-fr/exchange/client-developer/legacy-protocols/how-to-authenticate-an-imap-pop-smtp-application-by-using-oauth | |||
* Tutorial to register an application and create a secret ID: https://learn.microsoft.com/fr-fr/azure/active-directory/develop/quickstart-register-app#register-an-application | |||
* A thread in forum is also available related to use of OAuth2 for SMTP and IMAP: https://www.dolibarr.org/forum/t/oauth-office-365-and-email-collector/23437 | |||
=== For Google === | === For Google === | ||
See https://support.google.com/cloud/answer/6158849 | |||
The following steps are: | |||
TODO | |||
The is some official documentation here: | |||
* See https://support.google.com/cloud/answer/6158849 | |||