Configuration pre-requisites by DMS
Common scenarios that may affect user access to documents in CoCounsel Knowledge Search and configuration requirements for different document management systems.
A user may experience an authorization issue and accompanying message if the underlying DMS requires additional configuration to utilize federated search in Knowledge Search.
Refer to your DMS on what to do if the DMS requires authorization outside of the user's control. Find instructions for specific repositories in the following sections and pass along to your organization's IT or DMS administrator.
Microsoft applications
- To turn on Federated search for Microsoft applications, your organization's Microsoft administrator will need to grant consent through the API permissions page of the application registration in the Microsoft Entra administrator center.
- Go to the main Azure portal and go to Microsoft Entra ID.
- SelectEnterprise Applications.
- UnderActivity, go toAdmin consent requestto view pending requests.
- Review the permissions requested and select the user request to proceed.
- Sign in with your Microsoft user credentials and choose to accept the request.
- Upon acceptance, the request will be removed from the list, and the Thomson Reuters Search Service will appear in theAll applicationsscreen, confirming authorization.
- Verify that the application ID matches the one associated with the Thomson Reuters Search Service, as follows: e5f35fb2-4017-4d17-b695-e8e5204bd454.
- Go to Knowledge Search, and have the user sign in with their normal username and password to connect CCD to SharePoint.
iManage cloud
- Go to Cloud iManage.
- Go toSettings, then selectApplications.
- Find the applications,Thomson Reuters - Search Service.
- For both applications, edit theStatusand set it toEnabled.
- Retry to register iManage Cloud in Knowledge Search.
iManage on-premise
iManage on-premise is another popular DMS that is widely used in the professional services environment, particularly in the legal sector. For Thomson Reuters customers that choose to connect iManage on-premise in Knowledge Search, refer to the following configuration instructions.
- Preconditions for iManage on-premise connection:For the iManage on-premise connection, a precondition is that the customer's iManage administrator (who has access to iManage Control Center) must set the following Redirect URL in the app authentication config:https://api.legalplatform.thomsonreuters.com/oauth/connect/callbackAnother precondition to connect to iManage on-premise is ensuring that the firm's firewall settings permit for inbound requests from the required sets of IPs.
- The iManage administrator creates and sets up application in iManage Control Center:An iManage administrator (user with access to Control Center) needs to create and configure an application to connect with Knowledge Search ().Configure the application as follows:
- Name:Representative name, at customer discretion.
- Client Id:A GUID is suggested. This value is later configured in Knowledge Search.
- Client Secret:A GUID is suggested. This value is later configured in Knowledge Search.
- Additional fields:Optional.
Authentication Configuration:- Authentication required:Yes
- Application type:Web
- Client Type:Confidential
- Redirect URL:https://api.legalplatform.thomsonreuters.com/oauth/connect/callback
- Client Secret expires:Never
- Allow refresh token:Yes
- Refresh token expiry:365 days
- Access token expiry:30 minutes
- Allow access to:All users
- Turn on iManage on-premise in CoCounsel Admin Center:The CoCounsel administrator at your organization should go toAdmin settingsin CoCounsel web application. SelectIntegrations, thenKnowledge Search.
- Set up iManage on-premise in Knowledge Search:InKnowledge Search, the administrator can selectSettingsto configure iManage. iManage on-premise users must enter the Client ID, Secret Key, and Base URL for the iManage instance.BaseURL value is the public domain of the iManage OnPrem instance, that is, https://imange.mycompany.com or https://mycompanyfiles.com contact your iManage administrator or IT area to obtain this information.For any other connection issue, consult your IT department to ensure that any security products, network policies, or other internal procedures are considered to permit the traffic request between Thomson Reuters search and auth services.The Grant Token Expiry Key is an iManage instance configuration that determines how much time the Work Server has to send and receive the response to and from Redis. The value is in seconds. The default and recommended value previously was 5. However, it has been increased to 60 due to some issues in cases of latency. Try configuring it to 60 (the new default) to avoid any issue when connecting the on-premise instance. Work Server service must be restarted to apply the change.For more references, visit iManage help.
- Other Knowledge Search users can select connect and sign in with individual credentials:After the Knowledge Search administrator configures the iManage on-premise instance, other Knowledge Search users at the organization can connect and sign in with their iManage credentials.