Overview
Legora's iManage integration allows your users to pull in documents directly from iManage.
Key Features
File and Folder Selection
The integration includes a file and folder picker, enabling users to upload documents from iManage into Legora.
Helps users navigate their document structure in iManage and select the desired files and folders.
Secure Authentication and Connectivity
Legora employs iManage’s native authentication system for secure user validation.
No user credentials are passed through Legora; instead, an access token is used to fetch and parse documents from iManage.
Compatibility
Compatible with both on-premises and cloud-based iManage deployments:
On-Premises Deployments: Requires a secure endpoint for Legora to access iManage.
Cloud Deployments: Pre-established connection for a seamless integration experience.
Deployment Timeline
The integration can be deployed within 7 days from when the following conditions are met:
A secure endpoint for Legora to access iManage (for on-premises deployments).
Registration of the Legora application in iManage.
The URL through which users access iManage.
Security Measures
Our approach to security is to eliminate all risks for our customers, taking the best measures possible to allow safe integration with customers’ sensitive information.
Key Security Measures:
Access Token Management: Legora acquires an access token through native iManage authentication (both SSO and email/password). Tokens expire after 30 minutes and are invalidated upon logout.
No Credential Storage: No user credentials are ever passed through Legora. Authentication occurs directly between a user’s client and their iManage instance.
Read-Only Operations: Only read operations are performed by Legora, ensuring that no information or documents in iManage can be modified or deleted.
Endpoints Used by Legora Backend
/auth/oauth2/token
/auth/oauth2/revoke-token
/api/v2/customers/{customerId}/dialog-tokens
/api
/work/api/v2/customers/{customerId}/libraries/{libraryId}/documents/{id}/download
/work/api/v2/customers/{customerId}/libraries/{libraryId}/folders/{id}/children
/work/api/v2/customers/{customerId}/libraries/{libraryId}/documents?containerId=id
Instructions
To enable the integration you will need to follow these steps:
User Access to iManage: Legora needs to redirect user browsers to a URL through which users can access iManage.
Network Access to iManage: Legora must be able to access iManage using the same URL that users have. Any network restrictions (e.g., VPN, IP whitelisting) must be addressed.
Application Registration in iManage:
Name: Legora
API Key: [Generate a key]
API Secret: [Generate a secret]
Application type: Web
Client Type: Public
Redirect URL: https://app.eu.legora.com/imanage (or
https://app.us.legora.com/imanage for US setups)
Client Secret: Same as “API Secret”
Client Secret Expires: Never
Allow Refresh Token: No
Access Token Expiry: [Set desired token expiry]
Allow Access To: All users (unless specifying a subset of users for the integration)
Send Details to your Legora Contact: When you've registered your application, send the following details to your Legora contact:
Client ID
Client Secret
Application Proxy Secret (Only special occasions)
Server URL
API Server URL (Often the same as Server URL)
Q&A
How does the file and folder picker work?
The file and folder picker allows users to navigate their iManage document structure and select specific files or folders to upload into Legora. Link to video showcasing the feature.
How does Legora ensure secure authentication?
Legora uses iManage’s native authentication system, acquiring an access token upon successful authentication. No user credentials are passed through Legora, enhancing security.
What are the key security measures taken by Legora?
Key measures include access token management, no credential storage, and read-only operations to ensure data security and integrity.
What are the requirements for integrating Legora with iManage?
Users must have access to iManage, Legora needs network access to iManage, and an application must be registered in iManage with specific values provided.
What are the differences between cloud and on-premises deployments?
Cloud deployments are simpler with pre-established connections, while on-premises deployments may require additional networking configuration.
Need additional support? Contact [email protected].