App Registration Window
Version Compatibility: 
Server version 6.0 or later Console version 6.0 or later.
The App Registration window specifies the application registration adTempus uses when it authorizes access to a cloud storage provider using OAuth.
By default adTempus connects to the provider using its own application registration. For some providers adTempus does not have an application registration, and you must register your own application with the provider. You can also use your own registration for other providers, for example if your organization's policies do not allow users to grant access to third-party applications.
The process for registering an application varies by provider. For more information refer to the documentation offered by the provider. For Google, refer to the Google application registration topic.
When you use your own application registration, the client secret is stored (encrypted) on the adTempus server, which uses it to obtain and refresh access tokens. The client secret is never sent from the server back to the Console.
Regardless of which application registration you use (ours or yours), the security tokens required to access the account are stored in your adTempus environment only, and authorizing the application does not make it possible for Arcana Development to access your account.
Use my own app registration
Check this box to use an application you have registered with the provider instead of the adTempus application registration. This box is checked and cannot be cleared for providers for which adTempus does not have an application registration.
Client ID
Enter the client ID (also called the application ID or API key) assigned by the provider when you registered your application.
Client Secret
Enter the client secret (also called the API secret or client password) assigned by the provider. The secret cannot be displayed once it has been saved. To change it, enter a new value. Some application registrations (including Microsoft) may not require a client secret.
Tenant
This option is available only for Microsoft. If your application registration is limited to a single organization (a single-tenant application), enter your tenant ID or domain name (for example, "contoso.onmicrosoft.com"). Leave the field blank to allow accounts from any organization.
Redirect URI
When you register your application with the provider, add this redirect URI to the registration if it requires one. After you sign in, the provider returns to this address on your computer to complete the authorization.
- For most providers the redirect URI is http://localhost, and adTempus uses any available port.
- For Microsoft, add the redirect URI under the "Mobile and desktop applications" platform.
- For Google, create a "Desktop app" OAuth client, which does not require you to register a redirect URI.
- Some providers (such as Dropbox) require the port to match exactly. In that case the URI includes the port number to register.
Scopes
Lists the permissions (scopes) that adTempus requests. Your application registration must allow these scopes. For Google, add them to the application's OAuth consent screen. OAuth can be used in several contexts within adTempus and each context requires different permissions. If you are using the same application registration in multiple contexts, be sure to configure your application registration with the scopes from all the contexts where it will be used:
- SMTP Servers (email send)
- Incoming E-Mail Servers (POP3 and IMAP mail retrieval)
- File Servers (cloud file providers)
If a Google application's publishing status is "Testing," Google expires its refresh tokens after 7 days, after which you will need to authorize again. To avoid this, publish the application. See Google Application Registration for more information.
After you change the application registration, you must click Authorize in the Cloud Storage Provider Properties window to authorize access again, because an access token issued to one application cannot be used by another.