Difference between revisions of "Google Workspace Integration"

[unchecked revision][checked revision]
 
(49 intermediate revisions by 4 users not shown)
Line 1: Line 1:
−
{{DISPLAYTITLE:Synchronizing User Accounts with G Suite}}
+
{{DISPLAYTITLE:Synchronizing User Accounts with Google Workspace}}
−
{{Directory Services Preamble|G Suite account}}
+
{{Directory Services Preamble|Google Workspace account|Google Workspace}}
 +
 
 +
<p class=msnote>Please note that on December 16th 2019, [https://go.mailstore.com/?lang=en&target=gsuite-lsa-restriction Google announced] to limit access to Google Workspace accounts for less secure apps in the future.  This affects any MailStore Server version prior to 13, which therefore will no longer be able to authenticate users against Google Workspace when trying to log into MailStore Server.
 +
<br/>
 +
<br/>
 +
In MailStore Server 13, support for modern authentication methods via OAuth 2.0 & OpenID Connect as per Google's recommendation was introduced. Although MailStore Server 13 still comes with support for IMAP-based authentication, this document only covers the setup using modern authentication methods as required by Google in the future.</p>
 +
 
 +
== Prerequisites, Recommendations, Limitations ==
 +
* To comply with Google's requirements for ''Authorized redirect URIs'' of  OAuth 2.0 clients, MailStore Server must be accessible via an URI that ends with a public top-level domain. This does not necessarily mean that it must  indeed be accessible from the Internet. Google uses the list from https://publicsuffix.org for validation.
 +
* For best user experience, the certificate used by MailStore Server should be trusted by all client and the used web browsers. Using a certificate that is signed by an trusted certificate authority or [[Using_Lets_Encrypt_Certificates|using Let's Encrypt certificates]] is highly recommended.
 +
* If users are supposed to login to MailStore Server from outside the organization's network without a VPN, using [[Accessing_the_Archive_with_the_MailStore_Client_software|MailStore Client]], [[Accessing_the_Archive_with_the_Microsoft_Outlook_integration|MailStore Outlook Add-in]] or the [[Accessing_the_Archive_with_MailStore_Web_Access|Web Access]], the URIs mentioned in this article must be resolvable via DNS on the Internet and port-forwardings to the MailStore Server computer must be set up on the firewall or router if necessary.
 +
* When using Google to authenticate users at login, [[Accessing_the_Archive_via_Integrated_IMAP_Server|accessing the archive via IMAP]] is not possible for technical reasons.
  
 
== Register Project with Google ==
 
== Register Project with Google ==
−
Irregardless of whether own or third-party applications such as MailStore are supposed to interact with a G Suite account through Google APIs, they must be registered as a project with Google first. This is necessary to ensure that access by external applications is limited to a minimum and that each application uses its own set of credentials to authenticate itself.
+
Regardless of whether own or third-party applications such as MailStore Server are supposed to interact with a Google Workspace account through Google APIs, they must be registered as a project with Google first. This is necessary to ensure that access by external applications is limited to a necessary  minimum and that each application uses its own set of credentials to authenticate with Google.
  
 
=== Create New Project ===
 
=== Create New Project ===
−
To register a project for MailStore with Google, and prepare the next steps, proceed as follows:
+
To register a project for MailStore Server with Google, proceed as follows:
  
−
* Go to the [https://console.developers.google.com/ Google Developers Console].
+
* Go to the [https://console.cloud.google.com Google Cloud Platform Console].
−
* If prompted, login using a Google Account of you G Suite organization. A user with administrative privileges is highly recommend.  
+
* If prompted, login using a Google account of you Google Workspace organization. Logging in with a user that has admin privileges is highly recommended.  
−
* If no project exists, click ''Create'' on the dashboard. Otherwise open the ''Project'' drop-down list in the header bar and click ''New Project''.
+
* If no project exists, click ''Create Project'' on the dashboard. Otherwise, open the project list by clicking on the project drop-down in the header bar and click ''New project''.
−
* Name the project, e.g. ''MailStore Server''. By default a random Project ID is assigned, which can be changed if desired.  
+
* Type in a meaningful name into the ''Project name'' field, e.g. <tt>MailStore Server</tt>.
 +
* Verify that ''Organization'' matches the desired organization and adjust the ''Location'' if needed.
 
* Click on ''Create''.
 
* Click on ''Create''.
−
* Once the project has been created, ''APIs & Services'' is shown.
+
 
−
* Make sure that you have selected the newly created project. You can change the project by using the drop-down list.
+
Once the project has been created, make sure that it is selected in the project drop-down list before proceeding.  
  
 
==== Add API Libraries ====
 
==== Add API Libraries ====
−
* Select ''Library'' from the left navigation pane.
+
* Open the ''Navigation menu'' (☰) and select ''APIs & Services'' > ''Library''.
−
* In the ''API Library'', enable ''Admin SDK'' and ''Gmail API''.
+
* In the ''API Library'', search and enable the following APIs and services:
−
* Return to the project's dashboard by clicking on ''Google APIs'' in the top navigation bar.
+
*: <tt>Admin SDK API</tt>
 +
*: <tt>Gmail API</tt>
  
 
==== Customize Consent Screen ====
 
==== Customize Consent Screen ====
−
* Select ''OAuth consent screen'' from the left navigation pane.
+
* Open the ''Navigation menu'' (☰) and select ''APIs & Services'' > ''OAuth consent screen''.
−
* Under ''User Type'' select ''Internal''.
+
* Under ''User Type'' select ''Internal''.
−
* Click ''Create''
+
* Click ''Create''.
−
* Fill in the an '''Application name''', e.g. "MailStore Server"
+
* Enter a meaningful name into the ''App name'' field, e.g. <tt>MailStore Server</tt>.
−
* Click ''Save''.
+
* Fill out the other fields according to the policies of your organization.
 +
* Click ''Save and Continue''.
 +
* In the next steps, directly click ''Save and Continue'' again as MailStore Server does not need users to authorize any scopes.
  
 
=== Create Service Account ===
 
=== Create Service Account ===
−
A service account is needed for MailStore Server to authenticate with Google and request authorization to use certain Google APIs. The following steps describe the creation of such a service account.
+
A service account is required for MailStore Server to authenticate with Google and request authorization to use certain Google APIs for synchronizing users and accessing mailboxes. Follow these steps to create such a service account.
  
−
* Go to the [https://console.developers.google.com/ Google Developers Console].
+
* Open the ''Navigation menu'' (☰) and select ''APIs & Services'' > ''Credentials''.
−
* Click on ''Credentials''' in the left navigation pane.
 
 
* Click ''+ Create Credentials'' and select ''Service account'' from the drop-down list.
 
* Click ''+ Create Credentials'' and select ''Service account'' from the drop-down list.
−
* On the ''Create service account'' screen, enter a name for the service account. The ''Service account ID'' gets updated automatically based on the service account name, but can be changed if desired.  
+
* On the ''Create service account'' page, enter a name for the service account, e.g. <tt>MailStore Server Service</tt>.
−
* Click on ''Continue''.
+
* You can leave the the service account id at default settings or customize it.
−
* The service account does not require permissions on project level, therefore do not select a role.
+
* Enter a description such as: <tt>Service account for MailStore Server to synchronize users and access mailboxes</tt>.
−
* Click on ''Continue''.
+
* Click ''Create and Continue''.
−
* Only grant other users access to this service account if absolutely necessary, which is typically not the case.
+
* The service account does not require permissions on project level, therefore do not select a role. Also, users do not need access to the service account, so no changes are needed in the ''Grant users access to this service account'' step.
−
* Click on ''Create Key'' in the ''Keys'' section.
+
* Click ''Done''.
−
* Select the ''JSON'' as key type and click on ''Create''.
+
* In the list of service accounts that is now displayed, click on the newly created service account to open its properties.
−
* The JSON file will be downloaded automatically. Save the JSON file (e.g. <tt>MailStore API Access-e035d2ad4f35.json</tt>) in a secure location as it allows access to cloud resources of your organization.
+
* Under ''Keys'' click on ''Add Key'' and select ''Create new key''.
−
* Click on ''Close'' and then on ''Done'' to finish the creation of credentials.
+
* Select ''JSON'' as key type and click ''Create''.
 +
* The JSON file will be downloaded automatically. Save the JSON file in a secure location as it allows access to cloud resources of your organization.
 +
* Click ''Close''.
 +
* Back under ''Details'', click ''Show Advanced Settings''.
 +
* In the ''Domain-wide Delegation'' section, copy the ''Client ID'' to the clipboard.
 +
* Open the [https://admin.google.com/ Google Workspace Admin Console] by clicking on the button and log in with your Google Workspace domain admin credentials.
 +
* Open the ''Navigation menu'' (☰) and select ''Security'' > ''Access and data control'' > ''API controls''.
 +
* Under ''Domain wide delegation'', click ''Manage domain wide delegation''.
 +
* On the ''Domain-wide delegation'' page, click ''Add new''.
 +
* Copy the ''Client ID'' of the OAuth 2.0 Client that is linked with the service account from the clipboard.
 +
* Under ''OAuth Scope'', add the following scopes:
 +
*: <tt><nowiki>https://mail.google.com/, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.directory.user.readonly</nowiki></tt>
 +
* Click ''Authorize''.
  
−
=== Perform Domain-Wide Delegation of Authority ===
+
=== Create OAuth 2.0 Client for User Authentication ===
−
To grant the service account domain-wide access to your G Suite account, so called domain-wide delegation must be enabled as described in these steps:
+
To allow users to log in to MailStore Server by authenticating with Google using the OpenID Connect mechanism, another OAuth 2.0 client must be created as described below.
  
−
* Click on the newly created service account to access its details.
+
* Go to the [https://console.cloud.google.com Google Cloud Platform Console].
−
* Click on ''Show Domain-wide Delegation''.
+
* Open the ''Navigation menu'' (☰) and select ''APIs & Services'' > ''Credentials''.
−
* Check the ''Enable G Suite Domain-wide Delegation'' box.
+
* Click ''+ Create Credentials'' and select ''OAuth client ID'' from the drop-down list.
−
* Click on ''Save''.
+
* Select ''Web application'' as ''Application type''.
 +
* Enter a ''Name'', e.g. <tt>MailStore Server OpenID Connect</tt>.
 +
* Click ''+ Add URI'' under ''Authorized redirect URIs''.
 +
* Enter the URI that is reachable by clients in the ''URIs'' field using the the following scheme:
 +
*:<tt>https://<fqdn>[:<port>]/oidc/signin</tt>
 +
*; with the following components:
 +
*: '''https://'''<br/>Specifying the protocol ''https://'' is mandatory. To prevent certificate warnings later at login, the [[MailStore_Server_Service_Configuration#Certificate|certificate used by MailStore Server]] must be trusted by all client and the used web browsers.  
 +
*: '''FQDN'''<br/>The fully qualified domain name of the MailStore Server computer, e.g. <tt>mailstore.example.com</tt>. This must be resolvable from all clients, from where users are supposed to log in to MailStore Server.
 +
*: '''Port'''<br/>The TCP port of MailStore Web Access (default: <tt>8462</tt>). This must match the port configured in the [[MailStore Server Service Configuration#Services|MailStore Server Service Configuration]] at ''Network Settings'' > ''Services'' > ''MailStore Web Access / Outlook Add-in (HTTPS)''. The TCP port is only required if it is different from the default port of the HTTPS protocol (443).
 +
*: '''/oidc/signin'''<br/>The path at which MailStore Server expects to receive the authentication response from Google via the web browser.
 +
* Click ''Create'' to finish.
 +
* Copy the client ID and client secret from the ''Your Client ID'' and ''Your Client Secret'' fields to a safe place (e.g. password safe or similar) and click ''OK''.
 +
<div class="resp-table">
 +
{| class="wikitable" style="font-size: 85%;"
 +
|+ Examples of valid redirect URIs
 +
|-
 +
! style="width:80px;" | Product
 +
! style="width:80px;" | FQDN
 +
! style="width:40px;" | Port
 +
! Resulting Redirect URI
 +
|-
 +
| align="center"| MailStore Server
 +
| align="center"| mailstore.example.com
 +
| align="center"| 8462
 +
| <code><nowiki>https://mailstore.example.com:8462/oidc/signin</nowiki></code><br/><br/>Redirect URI with fully qualified domain name and MailStore Web Access default port.
 +
|-
 +
| align="center"| MailStore Server
 +
| align="center"| mailstore.example.com
 +
| align="center"| 443
 +
| <code><nowiki>https://mailstore.example.com/oidc/signin</nowiki></code><br/><br/>If the HTTPS default port 443 is used for MailStore Web Access or as source of a port forwarding rule on a firewall, specifying the port as part of the redirect URI can be omitted.
 +
|-
 +
| align="center"| MailStore SPE
 +
| align="center"| archive.example.com
 +
| align="center"| 443
 +
| <code><nowiki>https://archive.example.com/<instanceid>/oidc/signin</nowiki></code><br/><br/>The ''instanceid'' of the instance is part of the Redirect URI.  
 +
|-
 +
|}
 +
</div>
  
−
As a result, a new ''OAuth 2.0 Client'' was created for the service account that has been created in the previous step.
+
== Configure MailStore Server ==
 +
After the project has been successfully set up on the Google side, MailStore Server can now be configured to synchronize and authenticate users with Google Workspace.
  
−
=== Creating OAuth 2.0 Client for User Authentication ===
+
{{Directory Services Accessing Configuration|Google Workspace|gapps_sync_01.png}}
−
To allow users to log into MailStore by authenticating with Google, another OAuth 2.0 Client must be created that is suitable for OpenID Connect.
 
  
−
* Click on ''Credentials''' in the left navigation pane.
+
=== Connection ===
−
* Click ''+ Create Credentials'' and select ''OAuth client ID'' from the drop-down list.
+
For synchronization, MailStore Server requires information on how to connect to the Google Workspace.
−
* Select ''Web application'' as ''Application type''.
 
−
* Enter a ''Name'', e.g. MailStore Server OpenID Connect.
 
−
* In the ''Authorized redirect URIs'' section, click on ''+ Add URI''.
 
−
* Enter the URI that is reachable by clients in the ''URIs'' field in the following scheme:
 
−
*:<tt>https://<host>.<domain.tld>[:<port>]/oidc/signin</tt>
 
  
−
== Granting Access on G Suite Account to Project ==
+
* '''Key ID'''<br/>To import the private key, select the JSON file hat has been generated by Google for the service account in the [[#Create_Service_Account|Create Service Account]] step.
−
Once created, grant the newly created project fine-grained access to your G Suite account by defining the Google APIs it is allowed to use.
+
* '''Service Account'''<br/>The service account is determined automatically from the JSON file.
 +
* '''User Name'''<br/>The email address of a Google Workspace Administrator (e.g. [email protected]).
  
−
* Open the [https://admin.google.com/ Google Admin console] and log in with a G Suite domain admin.
+
=== User Database Synchronization ===
−
* Select ''Security'' > ''API controls'' from the menu.
+
After configuring the connection settings as described above, you can specify filter criteria for the Google Workspace synchronization in this section.
−
* Unter ''Domain wide delegation'', click ''Manage domain wide delegation''.
 
−
* On the ''Domain-wide delegation'' page, click ''Add new''.
 
−
* Enter the ''Client ID'' of the OAuth 2.0 Client that is linked with the service account.
 
−
* Under ''OAuth Scope'', add the following scopes:
 
−
*: <tt><nowiki>https://mail.google.com/, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.directory.user.readonly</nowiki></tt>
 
−
* Click ''Authorize''.
 
−
 
 
−
== Accessing Directory Service Integration ==
 
−
{{Directory Services Accessing Configuration|G Suite|gapps_sync_01.png}}
 
  
−
== Connection to G Suite ==
+
* '''Sync only these groups'''<br/>Choose one or several Google Workspace groups if you only want their members to be created as MailStore Server users. That way it's possible to exclude certain users from being synchronized to MailStore Server.
−
For synchronization MailStore Server requires information on how to connect to the G Suite.  
 
  
−
*'''Key ID'''<br/>To import the private key, select the JSON file (e.g. <tt>MailStore API Access-e035d2ad4f35.json</tt>) that has been generated by Google for the service account.
+
=== Authentication ===
−
*'''Service Account'''<br/>The service account is determined automatically from the JSON file.
+
The authentication settings define how MailStore Server should authenticate users at login, that have been synchronized from Google Workspace.
−
*'''User Name'''<br/>The ''email address'' of a G Suite Administrator (e.g. ''[email protected]'').
 
  
−
=== User Database Synchronization ===
+
* '''Method'''<br/>Ensure that ''OpenID Connect'' is selected. As mentioned in the introduction, the ''IMAP'' option is only available for backward compatibility.
−
After configuring the connection settings as described above, you can specify filter criteria for the G Suite synchronization in this section.
+
* '''Client ID'''<br/>Enter the client ID from the [[#Create_OAuth_2.0_Client_for_User_Authentication|Create OAuth_2.0 Client…]] step.
 +
* '''Client Secret'''<br/>Enter the client secret from the [[#Create_OAuth_2.0_Client_for_User_Authentication|Create OAuth_2.0 Client…]] step.
 +
* '''Redirect URI'''<br/>Enter the same redirect URI as defined in the [[#Create_OAuth_2.0_Client_for_User_Authentication|Create OAuth 2.0 Client…]] step .
  
−
*'''Sync only these groups'''<br/>Choose one or several G Suite groups if you only want their members to be created as MailStore Server users. That way it's possible to exclude certain users from being synchronized to MailStore Server.
+
{{Directory Services Options|Google Workspace Account}}
−
{{Directory Services Options|G Suite Account}}
+
{{Directory Services Assign Default Privileges|Google Workspace Account}}
−
{{Directory Services Assign Default Privileges|G Suite Account}}
+
{{Directory Services Run Synchronization|Google Workspace Account}}
−
{{Directory Services Run Synchronization|G Suite Account}}
 
 
[[File:ApplicationIntegration_sync_02.png|450px|center]]
 
[[File:ApplicationIntegration_sync_02.png|450px|center]]
−
 
  
 
{{Directory Services Test Authentication}}
 
{{Directory Services Test Authentication}}
−
<p class="msnote">'''Important Notice:''' For authentication with G Suite to work, the setting ''Allow less secure apps'' of the respective G&nbsp;Suite user has to turned on if it has not been enforced for all users (see above).</p>
+
[[de:Google Workspace-Integration]]
−
{{Directory Services Login with Directory Services Credentials|G Suite Account|mads_ldapauth_01.png}}
+
[[en:Google Workspace Integration]]
−
[[de:G Suite-Integration]]
 
−
[[en:G Suite Integration]]
 

Latest revision as of 10:31, 14 May 2022

In addition to adding users manually as described in chapter User Management, MailStore Server can synchronize its internal user database with the Google Workspace account of your organization.

During synchronization, user information, such as user names and email addresses, is copied from the Google Workspace account into MailStore Server's user database. That way, users can use their Google Workspace credentials to also log on to MailStore Server and emails can be assigned to their corresponding user archives automatically, for example. No changes are made to the Google Workspace account itself by MailStore Server. The scope of the synchronization can be limited through filters.


Please note that on December 16th 2019, Google announced to limit access to Google Workspace accounts for less secure apps in the future. This affects any MailStore Server version prior to 13, which therefore will no longer be able to authenticate users against Google Workspace when trying to log into MailStore Server.

In MailStore Server 13, support for modern authentication methods via OAuth 2.0 & OpenID Connect as per Google's recommendation was introduced. Although MailStore Server 13 still comes with support for IMAP-based authentication, this document only covers the setup using modern authentication methods as required by Google in the future.

Prerequisites, Recommendations, Limitations

  • To comply with Google's requirements for Authorized redirect URIs of OAuth 2.0 clients, MailStore Server must be accessible via an URI that ends with a public top-level domain. This does not necessarily mean that it must indeed be accessible from the Internet. Google uses the list from https://publicsuffix.org for validation.
  • For best user experience, the certificate used by MailStore Server should be trusted by all client and the used web browsers. Using a certificate that is signed by an trusted certificate authority or using Let's Encrypt certificates is highly recommended.
  • If users are supposed to login to MailStore Server from outside the organization's network without a VPN, using MailStore Client, MailStore Outlook Add-in or the Web Access, the URIs mentioned in this article must be resolvable via DNS on the Internet and port-forwardings to the MailStore Server computer must be set up on the firewall or router if necessary.
  • When using Google to authenticate users at login, accessing the archive via IMAP is not possible for technical reasons.

Register Project with Google

Regardless of whether own or third-party applications such as MailStore Server are supposed to interact with a Google Workspace account through Google APIs, they must be registered as a project with Google first. This is necessary to ensure that access by external applications is limited to a necessary minimum and that each application uses its own set of credentials to authenticate with Google.

Create New Project

To register a project for MailStore Server with Google, proceed as follows:

  • Go to the Google Cloud Platform Console.
  • If prompted, login using a Google account of you Google Workspace organization. Logging in with a user that has admin privileges is highly recommended.
  • If no project exists, click Create Project on the dashboard. Otherwise, open the project list by clicking on the project drop-down in the header bar and click New project.
  • Type in a meaningful name into the Project name field, e.g. MailStore Server.
  • Verify that Organization matches the desired organization and adjust the Location if needed.
  • Click on Create.

Once the project has been created, make sure that it is selected in the project drop-down list before proceeding.

Add API Libraries

  • Open the Navigation menu (☰) and select APIs & Services > Library.
  • In the API Library, search and enable the following APIs and services:
    Admin SDK API
    Gmail API

Customize Consent Screen

  • Open the Navigation menu (☰) and select APIs & Services > OAuth consent screen.
  • Under User Type select Internal.
  • Click Create.
  • Enter a meaningful name into the App name field, e.g. MailStore Server.
  • Fill out the other fields according to the policies of your organization.
  • Click Save and Continue.
  • In the next steps, directly click Save and Continue again as MailStore Server does not need users to authorize any scopes.

Create Service Account

A service account is required for MailStore Server to authenticate with Google and request authorization to use certain Google APIs for synchronizing users and accessing mailboxes. Follow these steps to create such a service account.

  • Open the Navigation menu (☰) and select APIs & Services > Credentials.
  • Click + Create Credentials and select Service account from the drop-down list.
  • On the Create service account page, enter a name for the service account, e.g. MailStore Server Service.
  • You can leave the the service account id at default settings or customize it.
  • Enter a description such as: Service account for MailStore Server to synchronize users and access mailboxes.
  • Click Create and Continue.
  • The service account does not require permissions on project level, therefore do not select a role. Also, users do not need access to the service account, so no changes are needed in the Grant users access to this service account step.
  • Click Done.
  • In the list of service accounts that is now displayed, click on the newly created service account to open its properties.
  • Under Keys click on Add Key and select Create new key.
  • Select JSON as key type and click Create.
  • The JSON file will be downloaded automatically. Save the JSON file in a secure location as it allows access to cloud resources of your organization.
  • Click Close.
  • Back under Details, click Show Advanced Settings.
  • In the Domain-wide Delegation section, copy the Client ID to the clipboard.
  • Open the Google Workspace Admin Console by clicking on the button and log in with your Google Workspace domain admin credentials.
  • Open the Navigation menu (☰) and select Security > Access and data control > API controls.
  • Under Domain wide delegation, click Manage domain wide delegation.
  • On the Domain-wide delegation page, click Add new.
  • Copy the Client ID of the OAuth 2.0 Client that is linked with the service account from the clipboard.
  • Under OAuth Scope, add the following scopes:
    https://mail.google.com/, https://www.googleapis.com/auth/admin.directory.group.readonly, https://www.googleapis.com/auth/admin.directory.user.readonly
  • Click Authorize.

Create OAuth 2.0 Client for User Authentication

To allow users to log in to MailStore Server by authenticating with Google using the OpenID Connect mechanism, another OAuth 2.0 client must be created as described below.

  • Go to the Google Cloud Platform Console.
  • Open the Navigation menu (☰) and select APIs & Services > Credentials.
  • Click + Create Credentials and select OAuth client ID from the drop-down list.
  • Select Web application as Application type.
  • Enter a Name, e.g. MailStore Server OpenID Connect.
  • Click + Add URI under Authorized redirect URIs.
  • Enter the URI that is reachable by clients in the URIs field using the the following scheme:
    https://<fqdn>[:<port>]/oidc/signin
    with the following components
    https://
    Specifying the protocol https:// is mandatory. To prevent certificate warnings later at login, the certificate used by MailStore Server must be trusted by all client and the used web browsers.
    FQDN
    The fully qualified domain name of the MailStore Server computer, e.g. mailstore.example.com. This must be resolvable from all clients, from where users are supposed to log in to MailStore Server.
    Port
    The TCP port of MailStore Web Access (default: 8462). This must match the port configured in the MailStore Server Service Configuration at Network Settings > Services > MailStore Web Access / Outlook Add-in (HTTPS). The TCP port is only required if it is different from the default port of the HTTPS protocol (443).
    /oidc/signin
    The path at which MailStore Server expects to receive the authentication response from Google via the web browser.
  • Click Create to finish.
  • Copy the client ID and client secret from the Your Client ID and Your Client Secret fields to a safe place (e.g. password safe or similar) and click OK.
Examples of valid redirect URIs
Product FQDN Port Resulting Redirect URI
MailStore Server mailstore.example.com 8462 https://mailstore.example.com:8462/oidc/signin

Redirect URI with fully qualified domain name and MailStore Web Access default port.
MailStore Server mailstore.example.com 443 https://mailstore.example.com/oidc/signin

If the HTTPS default port 443 is used for MailStore Web Access or as source of a port forwarding rule on a firewall, specifying the port as part of the redirect URI can be omitted.
MailStore SPE archive.example.com 443 https://archive.example.com/<instanceid>/oidc/signin

The instanceid of the instance is part of the Redirect URI.

Configure MailStore Server

After the project has been successfully set up on the Google side, MailStore Server can now be configured to synchronize and authenticate users with Google Workspace.

  • Log on to MailStore Client as a MailStore Server administrator.
  • Click on Administrative Tools > Users and Archives > Directory Services.
  • In the Integration section, change the directory service type to Google Workspace.
Gapps sync 01.png


Connection

For synchronization, MailStore Server requires information on how to connect to the Google Workspace.

  • Key ID
    To import the private key, select the JSON file hat has been generated by Google for the service account in the Create Service Account step.
  • Service Account
    The service account is determined automatically from the JSON file.
  • User Name
    The email address of a Google Workspace Administrator (e.g. [email protected]).

User Database Synchronization

After configuring the connection settings as described above, you can specify filter criteria for the Google Workspace synchronization in this section.

  • Sync only these groups
    Choose one or several Google Workspace groups if you only want their members to be created as MailStore Server users. That way it's possible to exclude certain users from being synchronized to MailStore Server.

Authentication

The authentication settings define how MailStore Server should authenticate users at login, that have been synchronized from Google Workspace.

Options

  • Automatically delete users in MailStore Server
    Here you can choose whether users that have been deleted in the Google Workspace Account will also be deleted in the MailStore Server user database by the synchronization. Users will also be deleted if they fall out of scope of the configured settings.
    Only MailStore Server users that have their authentication method set to Directory Services will be deleted.
    If the archive folder of such a user already contains archived emails, only the user entry but not its archive folder will be deleted in MailStore Server.

Assigning Default Privileges

By default, users that have been synchronized to MailStore Server from Google Workspace Account have the privilege to log on to MailStore Server as well as read access to their own user archive.
You can configure those default privileges before synchronization, for example, to assign the privilege Archive E-mail to all new users. To do this, click on Default Privileges...
More information on managing user privileges and their effects is available in the chapter Users, Folders and Settings which also has details on editing existing privileges.

Running Directory Services Synchronization

Click on Test Settings to check synchronization configuration and the results returned by the Google Workspace Account without any changes to the MailStore Server user database being actually committed.

To finally run the synchronization, click on Synchronize now. The results are shown with any changes committed to the MailStore Server user database.

ApplicationIntegration sync 02.png

You can test the authentication for a user by first selecting him from the list and then clicking on the button on the lower left. You will now be asked for that user's password. Upon clicking OK you'll receive a message whether the authentication has been successful.

Retrieved from "https://help.mailstore.com/en/server/index.php?title=Google_Workspace_Integration&oldid=7163"