To enable the ability to approve or reject changes through Gmail, you need to:
• |
• |
For best practice information on securely using API keys see the Google Support documentation (https://support.google.com/googleapi/answer/6310037?hl=en&ref_topic=7013279).
2 |
Open https://console.cloud.google.com/apis/credentials. Review the Terms of Service and click Agree and Continue. |
3 |
Select a project and click New Project. |
5 |
Click Create Credentials | OAuth client ID. |
6 |
Click CONFIGURE CONSENT SCREEN. |
7 |
Select the user type and click CREATE. |
8 |
Enter the application name on the OAuth consent screen and click SAVE AND CONTINUE. Although some fields are optional, the following information is required: |
• |
9 |
To add the GMAIL API from the library, select ADD OR REMOVE SCOPES, click Google API Library link, enter GMAIL API in the Filter field, choose Gmail API, and click Enable. |
11 |
Check the Read, compose, send, and permanently delete all your email from Gmail checkbox, then click UPDATE. |
12 |
Click SAVE AND CONTINUE to select your test users. |
13 |
Click ADD USERS. |
14 |
Enter the required account’s email and click ADD. (At a minimum, the account used to connect must be assigned as the test user.) |
15 |
Click SAVE AND CONTINUE to review your settings. |
16 |
Click BACK TO DASHBOARD. |
17 |
18 |
Click CREATE CREDENTIALS. |
19 |
20 |
21 |
Click Download to download the credential information in JSON format. |
1 |
Log into the Azure Active Directory portal (https://portal.azure.com/) with your global administrator user account. |
2 |
In the Microsoft Azure dashboard, go to Azure Active Directory | App registrations, and click New Registration. |
4 |
Under Supported account types, select Accounts in this organizational directory only (Single tenant) for the accounts that can access the application API. |
5 |
Leave the Redirect URI (optional) field empty. |
6 |
Click Register. |
7 |
On the Overview tab, go to View API Permissions. Click Add a permission, click Microsoft Graph | Application Permissions and add the Mail.ReadWrite and Mail.Send permissions. See Microsoft documentation for details on limiting permissions to specific Exchange Online mailboxes. (Note: The Enforce approver account validation option found when configuring email notifications will not function if you select to follow the Microsoft article to restrict access to a single mailbox.) |
8 |
Click Add Permission. |
9 |
10 |
Click Yes to confirm. |
11 |
On the preview screen, click Overview, and note the application ID and the directory ID. (You will need these values when setting up OAuth authentication.) |
12 |
Before setting up SQL replication, ensure the following is in place:
1 |
Right-click the required server and select Configure Database Replication (or Remove Replication if it is no longer required.) |
2 |
If configuring replication, select the subscribers to replicate the database with using the Add or Remove buttons, and click OK. |
NOTE: Upgrade considerations
|
f |
Choose Full Mesh topology. |
a |
Right-click the Replication node and Configure Distribution -> This machine should be its own Distributor. |
b |
Publication Type page: Choose Merge publication. |
c |
Subscriber Types page: Choose SQL Server 2008 or later. |
i |
Wizard actions: Select Create the publication. |
7 |
Refresh the Local Publications node, then expand and select the new publication. |
8 |
Right-click the publication and choose View Snapshot Agent Status. |
9 |
Right-click the publication and choose New Subscriptions. (All subscriptions can be created from here.) |
a |
b |
Merge Agent Location page: Choose Run all agents at the Distributor to create a similar replication path as the peer-to-peer setup. |
c |
Subscribers page: Click Add SQL Server Subscriber once for each SQL server in the replication. Choose the database on the target server for replication. |
e |
f |
g |
Subscription Type page: The Subscription Type should be Server. Set the Priority for Conflict Resolution to a different number for each subscription. |
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center