BSS Notification Email Authorization Protocols

Owned by Panagiotis Papanastasiou
Last updated: Oct 27, 2023 by Oleg Melnykov
3 min read

On this page, we analyze the different email authorization protocols of a BSS organization that can be configured and utilized for the secure dispatch of notification emails.

 

The Email Preferences of an organization in BSS govern the means for the dispatching of notification emails. Consequently, the focus on extra security measures has led us to provide you with the most modern and secure authentication protocol mechanisms for dispatching notification emails. These modern authentication mechanisms support the same protocol named OAuth 2.0 which supports the IMAP, POP, and SMTP e-mail transfer protocols. The two available authentication mechanisms that BSS supports are the Gmail (OAuth 2.0), and the Office 365 (OAuth 2.0), so that the BSS user can choose between them.

 

Locating the Email Preferences of Organizations

By navigating to BSS Setup > Administration > System Options > Organization Profile, at the bottom of the page, the section Email Preferences is where the Authorization Protocol options are located.

 

Choosing an Email Authorization Protocol

Currently, there are three available email authorization protocols.

  1. Standard: This protocol is used by default but it is less secure since it does not support the OAuth 2.0 protocol. This Standard form requires the Email Address as well as the Email Password in order to function. Also, the relative information of the Mail Server must also be provided manually by the BSS user, depending on the type of Mail Server he chooses to utilize.

     

  2. Google (OAuth 2.0): This protocol is the most modern and secure authentication offering supported by Google. Instead of the classic Password, this authentication protocol requires the Email Address as well as a ClientId, and a Secret in order to function. All those requirements are then used for the last step which is the Authorization.

     

  3. Office 365 (OAuth 2.0): This protocol is the most modern and secure authentication offering supported by Microsoft. Instead of the classic Password, this authentication protocol requires the Email Address as well as a ClientId, a TenantId, and a Secret in order to function.

     

As it is evident from the three distinct options of the Authorization Protocol drop-down menu that there are certain differences and similarities concerning the Email Preferences fields depending on the authentication option the BSS user chooses. The following section offers guides so that the configuration of each authentication option becomes easier.



Configuring the Authorization Protocols

  1. For the Standard authorization protocol, the configuration is a straightforward process where the BSS user must set the Mail Server field (SMTP, IMAP, POP3) and according to the requirements of the preferred mail server, define the rest of the fields, such as the Encryption and the Email Port. Then all the BSS user has to do is to provide the Email Address and the Password, and lastly, Save the changes.

  2. For configuring the Google (OAuth 2.0) authorization protocol, please continue to the following analytical guide. → https://interworkscloud.atlassian.net/wiki/spaces/ICPD/pages/524124161/Google+OAuth+2.0+Encryption

  3. For configuring the Office 365 (OAuth 2.0) authorization protocol, please continue to the following analytical guide. → https://interworkscloud.atlassian.net/wiki/spaces/ICPD/pages/524026239/Office+365+OAuth+2.0+Encryption