Implementing an Application Integration Server - Revision history

Ltalaschus at 14:39, 19 April 2017

2017-04-19T14:39:14Z

Ltalaschus: /* Python */

2017-04-19T14:38:28Z

Python

Dweuthen at 16:23, 23 March 2017

2017-03-23T16:23:13Z

Dweuthen: /* Example Server Implementations */

2015-09-15T15:26:49Z

Example Server Implementations

Dweuthen: /* Application Integration Server Implementations */

2015-09-15T15:25:02Z

Application Integration Server Implementations

Dweuthen at 15:20, 15 September 2015

2015-09-15T15:20:28Z

Dweuthen at 15:26, 23 March 2015

2015-03-23T15:26:05Z

Dweuthen: Dweuthen moved page Application Integration to Implementing an Application Integration Server: Using the Application Integration Server is now covered by the MailStore Server help

2015-03-23T15:18:24Z

Dweuthen moved page Application Integration to Implementing an Application Integration Server: Using the Application Integration Server is now covered by the MailStore Server help

Dweuthen at 10:44, 1 July 2014

2014-07-01T10:44:57Z

Dwarren at 07:25, 25 February 2014

2014-02-25T07:25:05Z

← Older revision		Revision as of 14:39, 19 April 2017
Line 160:		Line 160:

	=== Python ===		=== Python ===
−	An implementation of a modular Application Integration Server written in Python can be found in the [[Media:Application-integration-server.zip] file.	+	An implementation of a modular Application Integration Server written in Python can be found in the [[Media:Application-integration-server.zip\|Application-integration-server.zip]] file.

← Older revision		Revision as of 14:38, 19 April 2017
Line 160:		Line 160:

	=== Python ===		=== Python ===
−	An implementation of a modular Application Integration Server written in Python can be found in the [~~ftp~~:~~//ftp.mailstore.com/pub/Scripts/Python/application-integration-server.zip application~~-integration-server.zip] file.	+	An implementation of a modular Application Integration Server written in Python can be found in the [[Media:Application-integration-server.zip] file.

← Older revision		Revision as of 16:23, 23 March 2017
Line 1:		Line 1:
−	The following describes how to implement your own Application Integration server to synchronize users from sources that are not natively supported by MailStore. This can be virtually any user database that can be accessed via programming or scripting languages, for instance SQL server databases or plain text files. Using an Application Integration server as a directory service for synchronization and authorization in a MailStore SPE Instance is described in [[~~Instance_Management_-_Instance_Administration#Inside_the_Instance\|~~Instance Administration ~~- Inside the Instance~~]].	+	The following describes how to implement your own Application Integration server to synchronize users from sources that are not natively supported by MailStore. This can be virtually any user database that can be accessed via programming or scripting languages, for instance SQL server databases or plain text files. Using an Application Integration server as a directory service for synchronization and authorization in a MailStore SPE Instance is described in [[Instance Administration]].

	Application Integration servers can be written in any programming or scripting language. They must either provide their own HTTP server interface or be accessible through an existing HTTP server.		Application Integration servers can be written in any programming or scripting language. They must either provide their own HTTP server interface or be accessible through an existing HTTP server.

← Older revision		Revision as of 15:26, 15 September 2015
Line 160:		Line 160:

	=== Python ===		=== Python ===
−	An implementation of a modular Application Integration Server written in Python can be in the [ftp://ftp.mailstore.com/pub/Scripts/Python/application-integration-server.zip application-integration-server.zip] file.	+	An implementation of a modular Application Integration Server written in Python can be found in the [ftp://ftp.mailstore.com/pub/Scripts/Python/application-integration-server.zip application-integration-server.zip] file.

@@ Line 155: / Line 155: @@
 </source>
-== Application Integration Server Implementations ==
+== Example Server Implementations ==
 === Python ===
-An example implementation written in Python can be in the [ftp://ftp.mailstore.com/pub/Scripts/Python/application-integration-server.zip application-integration-server.zip] file.
+An implementation of a modular Application Integration Server written in Python can be in the [ftp://ftp.mailstore.com/pub/Scripts/Python/application-integration-server.zip application-integration-server.zip] file.

@@ Line 3: / Line 3: @@
 Application Integration servers can be written in any programming or scripting language. They must either provide their own HTTP server interface or be accessible through an existing HTTP server.
-=== Synchronizing Users ===
+== Synchronizing Users ==
 The Application Integration server must accept the following parameter via HTTP POST request to initialize the synchronization.
@@ Line 82: / Line 81: @@
 </source>
-=== Authenticating Users ===
+== Authenticating Users ==
 The Application Integration server must accept the following parameters via HTTP POST request to authenticate users.
@@ Line 155: / Line 154: @@
+}
 </source>

@@ Line 1: / Line 1: @@
-In addition to adding users manually, an instance can synchronize its internal user database with different directory services like Active Directory, MDaemon, IceWarp MailServer or Kerio Connect.
+The following describes how to implement your own Application Integration server to synchronize users from sources that are not natively supported by MailStore. This can be virtually any user database that can be accessed via programming or scripting languages, for instance SQL server databases or plain text files. Using an Application Integration server as a directory service for synchronization and authorization in a MailStore SPE Instance is described in [[Instance_Management_-_Instance_Administration#Inside_the_Instance|Instance Administration - Inside the Instance]].
-The following describes how to synchronize users from sources that are not natively supported by MailStore Service Provider Edition. This can be virtually any user database that can be accessed via programming or scripting languages, for instance SQL server databases or plain text files.
+Application Integration servers can be written in any programming or scripting language. They must either provide their own HTTP server interface or be accessible through an existing HTTP server.
 === Synchronizing Users ===
@@ Line 161: / Line 155: @@
+}
 </source>

← Older revision	Revision as of 15:18, 23 March 2015
(No difference)

@@ Line 3: / Line 3: @@
 The following describes how to synchronize users from sources that are not natively supported by MailStore Service Provider Edition. This can be virtually any user database that can be accessed via programming or scripting languages, for instance SQL server databases or plain text files.
-= Implementing an Application Integration Server =
+== Implementing an Application Integration Server ==
 Before connecting an instance to a user directory using the Application Integration, an appropriate Application Integration server has to be created first.
@@ Line 9: / Line 9: @@
 Application Integration servers can be written in any programming or scripting language. They must either provide their own HTTP server interface or be accessible via an existing HTTP server.
-== Synchronizing Users ==
+=== Synchronizing Users ===
 The Application Integration server must accept the following parameter via HTTP POST request to initialize the synchronization.
@@ Line 40: / Line 40: @@
 |}
-== Example ==
+=== Example ===
 <source lang="xml" toolbar="false" gutter="false">
 POST /mailstore-integration/index.php HTTP/1.1
@@ Line 55: / Line 55: @@
 </source>
-=== HTTP Response ===
+==== HTTP Response ====
 <source lang="xml" toolbar="false" gutter="false">
 HTTP/1.1 200 OK
@@ Line 89: / Line 88: @@
 </source>
-== Authenticating Users ==
+=== Authenticating Users ===
 The Application Integration server must accept the following parameters via HTTP POST request to authenticate users.
@@ Line 116: / Line 115: @@
 |}
-== Examples ==
+=== Examples ===
 <source lang="xml" toolbar="false" gutter="false">
 POST /mailstore-integration/index.php HTTP/1.1
@@ Line 131: / Line 130: @@
 </source>
-=== HTTP Response - Authentication Successful ===
+==== HTTP Response - Authentication Successful ====
 <source lang="xml" toolbar="false" gutter="false">
 HTTP/1.1 200 OK
@@ Line 148: / Line 146: @@
 </source>
-=== HTTP Response - Authentication Failed ===
+==== HTTP Response - Authentication Failed ====
 <source lang="xml" toolbar="false" gutter="false">
 HTTP/1.1 200 OK
@@ Line 165: / Line 162: @@
 </source>
-= Using the Application Integration =
+== Using the Application Integration ==
 During synchronization, user information such as user names and email addresses are read and recorded in the instance's user database. No changes are made to the source database where user information is synchronized from.
-== Accessing Directory Service Integration ==
+=== Accessing Directory Service Integration ===
 * Log on to the MailStore Service Provider Edition instance as an administrator.
 * Click on ''Administrative Tools'' > ''Users and Privileges'' and then on ''Directory Services''.
 * In the ''Integration'' section, change the directory service type to ''Application Integration''.
-== Connection ==
+=== Connection ===
 For synchronization, the instance requires information on how to connect to the Application Integration server.
@@ Line 183: / Line 179: @@
 * '''Password'''<br/>Password for basic authentication to access the given URL.
-== Options ==
+=== Options ===
 * '''Automatically delete users in MailStore Server'''<br/>Here you can choose whether users whose accounts have been deleted in the source database will also be deleted in MailStore Server's user database by the synchronization. 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. Additionally, only MailStore Server users that have their authentication method set to ''Directory Services'' will be deleted.
-== Assign Default Privileges ==
+=== Assign Default Privileges ===
 By default, users that have been synchronized to an instance have the privilege to log on 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...''
-== Run Directory Services Synchronization ==
+=== Run Directory Services Synchronization ===
 Click on ''Test Settings'' to check synchronization configuration and the results returned by the Application Integration server without any changes to the instance's user database being actually committed.
 To finally run the synchronization, click on ''Synchronize now''. The results are shown with any changes committed to the instance's user database.

@@ Line 36: / Line 36: @@
 | string ''(optional)''
 |-
-| <tt>smtpAddresses</tt>
+| <tt>emailAddresses</tt>
 | array ''(optional)''
 |}
@@ Line 72: / Line 72: @@
      "distinguishedName": "UID=john.doe,DC=example,DC=com",
      "fullName": "john.doe",
-     "smtpAddresses": [
+     "emailAddresses": [
        "john.doe@example.com",
        "john@example.com"
@@ Line 81: / Line 81: @@
      "distinguishedName": "UID=jane.doe,DC=example,DC=com",
      "fullName": "jane.doe",
-     "smtpAddresses": [
+     "emailAddresses": [
        "jane.doe@example.com",
        "jane@example.com"