The sign-in procedure to follow is dependent on whether you're connecting to an on-premises IRM Server, or IRM Service in the Cloud. If you're unsure of which of these is applicable to you, contact your system administrator for advice on how to proceed.

For more information, refer to Logging In to connect to IRM Service in the Cloud

Logging in to connect to IRM Service in the Cloud

The sign-in procedure to follow when connecting to IRM Service in the Cloud also depends on the type of authentication in place:

Standard login

  1. Perform a Windows search for "IRM Desktop Client" and select IRM Desktop Client for Records Managers. The Records Manager sign-in dialog opens.

  2. Enter your user name, password, name of the Records Manager cluster, and the domain name as outlined below. (You can obtain this information from your system administrator.)

    1. For User Name, provide the ID of the intended IRM account.

    2. For Password, provide the IRM password associated with the account.

    3. For Cluster, provide the IRM cluster name.

      Example: 
      companyname-cms.imanage.work

    4. For Domain, provide the Domain profile of the intended IRM account. As Domain isn't a required attribute when creating accounts in IRM, the field may be left blank if not relevant. (To assess this, you can observe the account using IRM Library Manager and check the Domain value set.)

      NOTE: Ensure that the typed value matches the exact Domain profile set for the IRM account. For example, an input domain value of companyname wouldn't be evaluated as a match for companyname.com.

  3. Select the Use Trusted Login check box if you want to be connected using your network user credentials. You don't need to enter a user name, password, or domain when this check box is selected.

NOTE: The Trusted Login functionality must be enabled on the (on-premises) Records Manager server to connect using this method.

  1. To suppress the Login dialog after successfully connecting to the Records Manager cluster, select the Automatically connect to cluster on startup check box. The sign-in credentials you entered are automatically sent to the Records Manager cluster on future sign-in attempts.
    If the sign-in fails, a dialog opens for you to re-enter the information manually.

NOTE: To disable the automatic connection functionality, hold down the Shift key while starting the application.

  1. Select OK.
    You remain connected to the Records Manager cluster until you close the application. To close the application, from the File menu, select Exit.

SAML login 

iManage Records Manager supports Secure Assertion Markup Language (SAML) for authentication. To sign-in using SAML:

  1. Perform a Windows search for "IRM Desktop Client" and select IRM Desktop Client for Records Managers. The Records Manager sign-in dialog opens.

  2. In the Records Manager sign-in dialog, select SAML Login.

  3. Enter the authorization server name, the connection port, and the name of the Records Manager cluster, as outlined below. (You can obtain this information from your system administrator.)

    1. For Authorization Server, enter your IRM Web URL, with the https:// part omitted.
      Example:
      yourcompany-irm.imanage.work

    2. For Port, enter: 443

    3. For Cluster, enter the IRM cluster name.  (As this field is auto-populated based on Authorization Server field input, you can amend the value as required.)

      Example:
      yourcompany-cms.imanage.work

  4. To suppress the sign-in dialog after successfully connecting to the Records Manager cluster, select the Automatically connect to cluster on startup check box. The sign-in credentials you entered are automatically sent to the Records Manager cluster. If the sign in fails, the dialog opens for you to reenter the information manually.

  5. Select OK.

    1. If the Identity Provider sign-in screen opens, proceed to Step 6 below.

    2. If the Identity Provider sign-in screen doesn't open:

      1. Close the IRM Desktop Client.

      2. Open the WOMDotNet.dll.config file, (which should be located in the ...\<username>\AppData\Roaming\iManage\RecordsManager folder — if not, refer to the note below)
        NOTE: If the WOMDotNet.dll.config file is located in the installation folder and not in the ...\<username>\AppData\Roaming\iManage\RecordsManager folder, it should be copied into the ...\<username>\AppData\Roaming\iManage\RecordsManager folder as part of the Desktop Client upgrade. For more information, refer to the Pre-Upgrade check: preservation of settings section in iManage Records Manager Upgrade Guide.

      3. Adjust the following values (as applicable):

        • <add key="interwoven.recordsmanager.controls.LoginPageDetectionThreshold" value="1"/>

        • <add key="interwoven.recordsmanager.controls.LoginPageDetectionTerms" value="login"/>

        as described:

        <!-- SAML login shows a browser to prompt for your IDP credentials. This setting determines how easily the browser appears.
        Values are 0, 1, or 2.
        0 - Will appear any time a web page finishes loading. Will result in the browser flashing up briefly if it navigates through intermediate pages before the final login page.
        Useful for debugging, if the login page never appears.
        1 - Same as 2, plus if the page text contains any of the terms LoginPageDetectionTerms.
        Useful if your IDP uses an iFrame to display the actual login fields.
        2 - Will only appear if the web page contains any visible html input fields. Suitable for ADFS. -->
        <add key="interwoven.recordsmanager.controls.LoginPageDetectionThreshold" value="1"/>
        <!-- Terms used for LoginPageDetectionThreshold setting 1. Comma-delimited and case-insensitive. -->
        <add key="interwoven.recordsmanager.controls.LoginPageDetectionTerms" value="login"/>

      4. Save the updated WOMDotNet.dll.config file.

      5. Restart the IRM Desktop Client.

      6. Repeat Steps 2 to 5 (above).

  6. Enter your Identity Provider sign-in credentials and select Sign in.