--- title: Resolve common issues for iManage description: Overview of common issues when setting up connection with iManage --- [Skip to content](https://help.henchman.io/migration/home/resolve-common-issues-for-imanage#main-content) English Show submenu for translations ![LOGO LEXISNEXIS.png\]](https://help.henchman.io/hs-fs/hubfs/LOGO%20LEXISNEXIS.png?height=40&name=LOGO%20LEXISNEXIS.png) - Open main navigation Close main navigation - - English Show submenu for translations - [Go to henchman.io](https://www.henchman.io/) [Go to henchman.io](https://www.henchman.io/) Hi! How can we help you today? - There are no suggestions because the search field is empty. 1. [Help Center](https://help.henchman.io/migration/home?hsLang=en) 2. [Technical Admin setup](https://help.henchman.io/migration/home/technical-admin-setup?hsLang=en) 3. [iManage On-Prem or iManage Work](https://help.henchman.io/migration/home/technical-admin-setup?hsLang=en#imanage-on-prem-or-imanage-work) - [Technical Admin setup](https://help.henchman.io/migration/home/technical-admin-setup?hsLang=en#main-content) - [Deploying the Add-on](https://help.henchman.io/migration/home/technical-admin-setup?hsLang=en#deploying-the-add-on) - [SharePoint Cloud (Service Account)](https://help.henchman.io/migration/home/technical-admin-setup?hsLang=en#sharepoint-cloud-service-account) - [SharePoint Cloud (Service Principal)](https://help.henchman.io/migration/home/technical-admin-setup?hsLang=en#sharepoint-cloud-service-principal) - [SharePoint On-Prem](https://help.henchman.io/migration/home/technical-admin-setup?hsLang=en#sharepoint-on-prem) - [iManage Cloud](https://help.henchman.io/migration/home/technical-admin-setup?hsLang=en#imanage-cloud) - [iManage On-Prem or iManage Work](https://help.henchman.io/migration/home/technical-admin-setup?hsLang=en#imanage-on-prem-or-imanage-work) - [NetDocuments](https://help.henchman.io/migration/home/technical-admin-setup?hsLang=en#netdocuments) - [Microsoft OneDrive](https://help.henchman.io/migration/home/technical-admin-setup?hsLang=en#microsoft-onedrive) - [GoogleDrive](https://help.henchman.io/migration/home/technical-admin-setup?hsLang=en#googledrive) - [Opentext eDocs](https://help.henchman.io/migration/home/technical-admin-setup?hsLang=en#opentext-edocs) - [Data Transfer](https://help.henchman.io/migration/home/technical-admin-setup?hsLang=en#data-transfer) - [Company administration](https://help.henchman.io/migration/home/company-administration?hsLang=en#main-content) - [Customizations](https://help.henchman.io/migration/home/company-administration?hsLang=en#customizations) - [User management](https://help.henchman.io/migration/home/company-administration?hsLang=en#user-management) - [Start using Lexis® Create DMS](https://help.henchman.io/migration/home/start-using-lexis-create-dms?hsLang=en) - [Tips & Tricks](https://help.henchman.io/migration/home/tips-tricks?hsLang=en) - [FAQ](https://help.henchman.io/migration/home/faq?hsLang=en) # Resolve common issues for iManage ## Overview of common issues when setting up connection with iManage #### Enabling the iManage refresh token In iManage older versions, the Refresh token needs to be enabled through the API.  From the following iManage help article: [https://help.imanage.com/hc/en-us/community/posts/360034796653-Rest-API-refresh-token-empty](https://help.imanage.com/hc/en-us/community/posts/360034796653-Rest-API-refresh-token-empty) The refresh token can be enabled for a registered application by making the following REST call with an admin token: ``` PUThttps://{server}/api/v2/customers/1/settings/{clientid}/oauth2.tokensPayload:{"type": "value","value":{"allow_refresh_token": true, "refresh_token_expiry": 14,"access_token_max_idle_time": 30}} ```   --- #### URL Base URL should be a valid URL ![](https://help.henchman.io/hs-fs/hubfs/Screenshot%202023-06-30%20at%2010-32-55-png.png?width=474&height=240&name=Screenshot%202023-06-30%20at%2010-32-55-png.png) - URL should start with **https://** - Please check if there aren't any unnecessary suffixes to the URL like /login or other. We only need the BASE url. We can only work with the base URL because we need to redirect to the right place.   - Make sure our IP addresses are **whitelisted** in case your URL is not publicly accessible. If this is not the case, we will not be able to connect to your iManage on-Premise server.   --- #### **HTTPS certificate issues** Ensure the following requirements are taken into account for the https certificate: - - Signed by a **recognized certificate authority**. The certificate chain must contain a root certificate from an established root CA (= Certificate Authority). - Ensure the full certificate chain is returned by your server. In most cases this translates to returning the following: - the server certificate - the intermediate CA certificate - and the root CA certificate - You can use the following command to check the validity: ``` openssl s_client -verify_return_error -connect : ```   --- #### Redirect Issues If your iManage instance is linked to an external SSO provider like Azure AD or Okta, it is important that the base URL of your iManage instance in Lexis® Create DMS is the same as the redirect url in your SSO provider. This can be resolved by entering the Internal URL for OAuth authentication in [Step 1 of setting up the connection. ](https://help.henchman.io/home/configure-the-application-imanage-on-prem?hsLang=en) - [![Chill listening crop-3](https://help.henchman.io/hs-fs/hubfs/HM-PNG---High-logo-word-dark-2.png?width=85&height=24&name=HM-PNG---High-logo-word-dark-2.png "Chill listening crop-3")](http://Henchman.io) Copyright © 2026, Lexis Create+,formerly Henchman