RapidIdentity Product Guide: New UI

Local File Server

The Local File Server is available with all RapidIdentity Rolling and LTS Release versions beginning with Rolling Release version 2018.5.2.

The Local File Server interface allows administrators to install an SMB file system to serve as a Windows-environment cluster shared file system.

Legacy_Local_File_Server.png

Installing the Local File server is best used for on-premises configurations and test environments , and the Local File Server can be installed in either of 2 places:

  1. A dedicated Windows File Share Server in the organization's environment.

  2. On the RapidIdentity appliance server that contains the RapidIdentity database.

If the dedicated Windows File Share Server is available in the organization's environment, option 1 is best. Otherwise, option 2 is sufficient, however, it is advisable to ensure sufficient disk space exists to allow for both database and RapidIdentity Connect logs to store. If possible, SNMP monitoring of the disk space is also advisable.

Post-installation, RapidIdentity will only ever expose one shared idautocluster and it will only be accessible by 1 user of the same name, and the Local File Server is not visible in the Windows Explorer Network Folder. It is necessary to know the Local File Server UNC path to access it, which is available in the Connection Info menu after installation.

Once the Local File Server is installed and configured in the Command Line Environment, it can be subsequently administered in either of 2 places, depending on UI: