iManage

Overview for configuring iManage to connect to CAM

CAM integrates with the iManage Work Cloud, Cloud iManage, and iManage on-premises environments.

Note: The procedure for configuring iManage Work Cloud/Cloud iManage and iManage on-premises is almost the same. You can still utilize the provide screenshots and steps for both.

Warning: The user, and not Litera, is responsible for creating the enterprise proxy application (because CAM/Litera is not the one deciding where their proxy connector is to be placed) AND then proceeding with the app registration steps.

Two apps are to be setup:

The enterprise proxy application
The app registration for CAM

To integrate CAM with the iManage Work Cloud, the iManage cloud servers must be configured using the below steps.
To connect an on-premises iManage environment, the iManage server needs to be accessible from the internet. This can be done as follows:
1. Expose the iManage Server via a static-ip/firewall. Click here for information on whitelisting CAM’s IP.
2. Use Azure Proxy.
3. Add trusted-ip restriction as an additional security measure.

You can add and manage multiple iManage servers, define the workspaces' naming convention, the template rules to be applied, and the default folder metadata.

Warning: The Client ID & the Client Secret ID must be updated in the iManage Control Center (IMCC) to support API Authentication and enable CAM to integrate with the iManage Server. Read here for detailed instructions to update the Client ID & Secret ID.

Configuring NRTAdmin Access

For iManage, create an NRTAdmin account role in iManage that does not have the View Document permission granted to the role. Assign this to the CAM iManage account. That allows CAM to read all metadata but cannot download or view the document or its content.

The NRTAdmin role assigned to the account must be granted permission to access iManage Control Center.

The NRT Admin account is necessary for the CAM connection to iManage in many modules!

This is so we can:

Provision workspaces: the ability to create, modify, secure, and delete workspaces.
Work with Metadata: the ability to create, modify and delete metadata
Manage Users/Groups: the ability to create, modify, disable & manage group memberships

Signs of a missing NRTAdmin acct or no Control Center access:

CAM can’t access iManage Control Center with the account.
Generate Template doesn’t return results.

iManage Configuration

iManage Token Expiry Extension

There are two ways to increase the Token Expiry for iManage, depending on what setup the client has used.

iManage Cloud steps

For iManage cloud, the configurations are made in IMCC.

a. Open IMCC

b. On the left navigation, open Settings-> Applications.

c. Open the Prosperoware CAM application (or the name for the CAM app that you have configured) from that page.

d. Find the Authentication section.

e. Click Edit.

f. The user can configure both the Refresh token expiry period and the access token expiry period.

iManage on-premises with Azure Proxy steps

For on-premises systems, this token is used in the External System Configuration-iManage panel.

a. First, ensure the Azure proxy application is configured: https://pdocs.atlassian.net/wiki/spaces/CCAM/pages/29491219/iManage#Azure-Proxy-Server-app

b. Update the Azure token period according to the Microsoft article here: Configurable Token Lifetimes - Microsoft identity platform / https://docs.microsoft.com/en-us/azure/active-directory/develop/configure-token-lifetimes

c. If not configured already, open the External System Configuration-Imanage window.

d. Click edit on the system to be configured.

e. Enter the application id, and click Get token. Now your token is provided.