Changes

====New Support for OAUTH Authentication for SMTP Relay and Migration of Credentials to Integration Keys====

New clients and clients transitioning from basic Added support for OAUTH 2.0 authentication for Office 365, Gmail, or other within the SMTP relay services must Relay integration functionality. This will allow you to now create an integration keyconfigure this alternative authentication method instead of the basic authentication that was previously the only option available.To do this, go to '''Global Settings''' > '''Integrations''' tab > '''Integration Key Management''' > Click the plus icon to create a new integration keyIntegration Key.In the '''Type''' dropdown, you will see two new options under the keystore category: "Basic Authentication" that represents the previously existing method for SMTP relay and the new "OAuth 2.0" for Gmail and Office 365 SMTP relay.

<uThe settings for existing configurations of SMTP Relay have been updated and moved. Where previously the authorization credentials were stored in the block of SMTP Relay settings in the '''Global Settings''' >'''NoteCommunications'''</u>: For tab, these have now been moved into the Integration Keys configuration area to better separate the management of credential secrets versus the OAuth 2integration behavior.0 optionAfter this update, you will can find your authentication credentials located in the Integration Keys area as a keystore, and in the '''Global Settings''' > '''Communications''' tab. You simply need to log in select the appropriate keystore and authorize during the setup processauthentication mechanism to easily manage this integration.

For clients using T2P, make sure to select the correct integration key in the SMTP relay settings located under '''Global Settings''' > '''Communications'''. Storing the username and password for SMTP relays in an integration key also provides enhanced encryption and decryptionor exclude this when you T2P.