Publisher requires that easendmail.exe is installed on the Publisher server.
- First, set up a project in Google Developers Console https://console.developers.google.com/
Then select that project
- Nagivate to APIs & Services -> Credentials -> Manage service accounts to add a new service account to this project
- Create new, fill out service account information by clicking the Create Service Account at the top
- Add the name you want for the service account display
-
It will take you back to service accounts, now click the Actions (ellipses) icon and select Manage keys
- Click the ‘Add key’ button, then ‘Create new key’, select .p12 and create
- Do not change the private key password, which should default to ‘notasecret’. Please note where the file downloads to, you will need the name of this file and then you need to move it into Windows\System32 on the Publisher's server.
- Once that is done, you will need to return to the ‘Service accounts’ page, click the service account where it is linked to pull up the Service account details. Then ‘Show domain-wide delegation’ and click to enable G Suite Domain-wide delegation, configure and save.
- In the details, please copy and save for now the Email and the Unique ID; we will need these later
- Now we will need to navigate to G Suite, at admin.google.com, go to Admin Console, click 'Security'
- It will ask you to verify your Google account by signing in
- If you do not have a Google Workspace account (regular Gmail accounts cannot be used) you will have the option to add an account
- go to Admin Console, click 'Security'
- Navigate to ‘API Controls’ and then click on button for ‘Manage domain-wide delegation’
- Click ‘Add new’, and in the ‘Client ID’, put in the ‘Unique ID’ that we noted from the service account before. In ‘OAuth Scopes’, input ‘https://mail.google.com/,email,profile’. Then ‘Authorize’.
- Now we just need to set up the email in the Supervisor Workstation. In SWS, navigate to Maintenance -> Setup -> Service Provider Devices.
- Protocol will be Email, Address will need to be the name of the .p12 file (including .p12; remember this file should be in the Windows\System32 directory), set ID to AUTH_OAUTH, use an account from your G Suite that has email access as Account Name. Password is NOT that account’s password; for the password, simply set the email address that we noted earlier from the service account. (In our example pictures, it would be ‘publisher@publisher-309313.iam.gserviceaccount.com’)
- Save, and the Report Publisher can now use gmail OAuth to send emails!
