Skip to main content
All CollectionsConnectors
On Premise API Push Connector: Technical Requirements verification
On Premise API Push Connector: Technical Requirements verification

Technical requirements verification: On Premise Push API

Kévin Joffray avatar
Written by Kévin Joffray
Updated over a week ago

Basic concept

This function is to benefit an automatic signature for OWA users (2010, 2013, 2016) where the Exchange Server is hosted locally on the customer's network.

Letsignit must declare an application for the client (appId and appSecret provided) on the Letsignit infrastructure.

Once declared, this application is allowed to operate with a Letsignit public API (reachable at

The script provided by Letsignit, adaptable to the client environment, creates a connection to the local Active Directory (Microsoft), collects the user emails and uses them to query the Letsignit server (HTTPS), collects the HTML signatures and copies them to the appropriate folder in the Exchange database.

To benefit from this function automatically, it will be possible to set it up as a scheduled task.

Script location

The script must be located on the local Exchange Server or remotely on a workstation that can run scripts and can join the local Exchange Server.

If the script is installed remotely from the Exchange Server, the "Exchange Server FQDN" and the "Credentials" (Login and password) must be entered in order to access to Exchange Server.

Technical requirements

  • Minimum Exchange Server version: Exchange 2010

  • Minimum script execution version for PowerShell: Version 4.0 recommended

  • Minimum PowerShell script execution policy for automation in a scheduled task (without confirmation and action from the user): RemoteSigned

  • PowerShell modules needed to execute and run the script:

    • RSAT-AD-PowerShell module (including all features)

    • Active Directory module

#API Push #API #Push #Connector #OWA #On premise #Onpremise

Did this answer your question?