31,028
edits
Module OAuth: Difference between revisions
Jump to navigation
Jump to search
m
→Generation of the token
mNo edit summary Tag: 2017 source edit |
Tag: 2017 source edit |
||
| Line 96: | Line 96: | ||
Note: If the goal if the OAuth entry is to be used for SSO Login, you don't need to generate the token. | Note: If the goal if the OAuth entry is to be used for SSO Login, you don't need to generate the token. | ||
Once your OAuth entry has been created, you can switch on the second tab to generate and get your OAuth token. | Once your OAuth entry has been created, you can switch on the second tab to generate and get your OAuth full token (a full token is the access token that expires after a short delay + a refresh token that allows to get a new access token once expired). | ||
This token will then be used by the other modules or features (for example, to send email using SMTP or to read emails using IMAP). | This full token will then be used by the other modules or features (for example, to send email using SMTP or to read emails using IMAP). | ||
'''Note about Google OAuth token duration''' | |||
- When your oauth entry is published is Testing, Google unverified, the refresh_token expires is 7 days and is limited to 100 access_token refreshes. | |||
- When your oauth entry is published in Production, Google verified, refresh_token expire is 180 days and has unlimited access_token refreshes. | |||
== External documentation == | == External documentation == | ||