The purpose of the document is to guide you through all the necessary steps that needs to be taken in order to enable Digizuite™ Office Connector on any computer inside your domain.

Introduction

The Digizuite Office Connector need to be configured to point to the right DAM with the appropriate access rights. This can be automatically configured at installation.
This guide is intended to outline how an IT department or similar resources can automate this.

Process overview

When the Office Connector installer script runs, it will look for a configuration file in the same directory where the installer resides. If the file exists, the installer will read the contents to enter these configuration parameters into the application.

Any parameter you enter to the configuration file will be applied to the installation. Therefore, it may be useful to supply the file to the receiving user in any case. Even just having the proper DAM URL pre-filled could ease the deployment.
Once the user opens the Office Connector plugin from within an Office Application, any of these parameters can be added or changed - such as userID and password.

The easiest deployment would be if the organization use SSO, or if all the Office Connector users use the same userID and login. In that case, no further action will be needed by the users once the installation has finished.

Configuration

To use this auto-configuration feature, you should start by entering the necessary configuration parameters in the config file. See below for the details.

XML mapping to config parameters

SSO (Single Signon-on considerations)

If your organization uses Single Sign On solutions in combination with your DAM solution, make sure you get the appropriate SSO configuration details from your Digizuite DAM consultant.

XML file format and Parameter details

The installer looks for a file named configuration.xml, inside the folder where the installation file resides.

The file has the following format:

<?xml version="1.0" encoding="utf-8"?>
<configuration>
<configSections>
<sectionGroup name="digiConfig">
<section name="services" type="DigiEyeZ.Framework.WebLibrary.Configuration.ServicesSection, Framework.WebLibrary" />
<section name="log" type="DigiEyeZ.Framework.Library.Configuration.LogSection, Framework.Library" />
</sectionGroup>
</configSections>
<digiConfig>
<services connectBindingName="WSHttpBinding_IConnect" searchBindingName="WSHttpBinding_ISearch" />
<log name="DigiZuiteMSOfficeConnector" path="%logroot%\DigiZuiteMSOfficeConnector" filter="Warning" />
</digiConfig>
<appSettings>
<add key="backendurl" value="" />
<add key="signonurl" value="" />
<add key="usesinglesignon" value="false" />
<add key="adfsstsfqdn" value="" />
<add key="useadfssts" value="false" />
<add key="uilanguage" value="en" />
<add key="credentials" value="" />
</appSettings>
<startup>
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0" />
</startup>
</configuration>

• backendurl – URL that points to Digizuite™ DAM Center 
  • Example: http://customer.dam.digizuite.com
• signonurl – URL of single sign on web service
  • Example: http://customer.dam.digizuite.com/Dmm3SSOWS/SingleSignOn.svc
  • The feature requires that DMM3SSOWS is configured to use Windows Login against Active Directory.
    • Note: the web service can be moved to an internal web server. If that would be the case, web.config must be modified. See comments in web.config.
• usesinglesignon – true/false
• adfsstsfqdn – domain name of STS service, if ADFS is used 
  • Example: sts.customer.com
• useadfssts – use ADFS STS for singe sign on – true/false
• uilanguage – language to be used: en, da, de, sv
• credentials – credentials to be used if common user is desired
  • Note: it contains encrypted credentials. Install DigiZuite™ Office Connector and fill in the credentials, then retrieve the value from: C:\Users\<user>\AppData\Local\DigiEyeZ\DigiZuiteMSOfficeConnector\ DigiZuiteMSOfficeConnector.config

Deployment

When distribution the plugin to be installed, include the file configuration.xml in the installation directory together with the connector installation file.