Before obtaining Oauth tokens, an application must be registered with your provider. For example, for Microsoft 365, an administrator can use 'App registrations' in the Azure Active Directory page.
The registration should be for an authorization code flow type with offline access, to enable tokens to be refreshed by the UnForm or CirrusPrint service. If redirect pages must be pre-registered, use this page.
Applications have authorization and token endpoints, as well as a scope, client ID, and client secret. Scope defines the permissions required for use by SMTP or IMAP access, with specifics defined by the provider. Help is provided (currently) for Microsoft 365. This information is used in two steps:
Enter this required information to authorize UnForm to access the services granted to it by the app registration. These values come from your provider's application registration. For example, in the Azure Active Directory app registration overview page and client secret page.
UnForm 10
Copy this data into an UnForm user record Notes field. When sending
or receiving mail, this user ID can be identified in the password
setting for the SMTP or IMAP setting as "password=oauth:userid".
If you plan to use unique From: addresses when sending email, you
may need to add Send As permission for the login user to the From user.
Important: Do not use an IMAP setting for a live user account,
as UnForm collects and removes all email from that mailbox.
CirrusPrint 3
For site or company email sending settings, paste SMTP information
into the OAuth Token Request Data field under Site, Configuration
or Company configuration. For email inbound sources, paste IMAP information
into the OAuth Token Request Data field in the inbound source page.