System Settings

Users

Overview of the User administration page. Here it’s possible to create, edit, and delete users. You can also reset their password from this page.

Notitie

When Active Directory integration is enabled, the users and managers are administrated through the Active Directory.

Users List

The listview provides administrators with some useful information and features. In the table the following columns are present:

  • Username

    Username of the user.

  • User E-mail

    E-mail address of the user.

  • Cases

    List of cases that the user has access to, separated by the pipe (“|”) symbol.

  • Created At

    Creation timestamp of the user.

  • Actions
    • Yellow key button: Reset a user’s password.

    • Blue paper button: Edit a user.

    • Red trashbin button: Delete a user.

Creating a user

Creating a user is done by clicking the green “Add New” button. A popup will open:

Simply fill in the following details, and click “Add User” when done.

  • Username

    Username for the new user. Must be unique. Is used for authentication.

  • Full Name

    Full name of the user. Is used for nicer displaying names of the user.

  • E-mail

    E-mail address of the user.

  • Password (2x)

    Choose a password for the user. Pick a strong password, as it can give access to documents.

  • Choose user role(s)

    Choose role(s) for the new user. There are four roles available:

    • Admin: Gives unlimited access to all cases, their data, and their management portals. Also grants access to administrator settings.

    • User: Basic user. Usually used for case reviewers etc. Restricted access.

    • Manage: Same as ‘User’ but with access to case management (setup, sources, settings, etc.).

    • Workflow: Role to give users access to the Workflow. When a lot of users need access to a workflow, this may be used to provide easier access setup in workflow configuration.

  • Case(s)

    Choose the case(s) that the user should have access to.

Editing a user

Editing a user is done by clicking the blue paper button in the “Actions” column of the “Users List”. A popup will open:

Here you can edit the settings of the user. When done, click “Edit user” to save the changes.

Deleting a user

Deleting a user is done by clicking the red trashbin button in the “Actions” column of the “Users List”.

A confirmation popup will open. Click “Delete” to permanently delete the user. This action cannot be undone.

Resetting a user’s password

Resetting a user’s password is done by clicking the yellow key button in the “Actions” column of the “Users List”. A popup will open:

Simply pick a new password, confirm it, and click “Reset Password”. The user can now authenticate using the new password.

Notitie

The user will not be notified by INDICA that their password has changed.

Resetting the admin password

When the password of the only Admin account has been lost, there is a way to reset the password.

To do this, SSH access and root-level permissions on the appliance are needed. When logged in into the appliance, navigate to the following directory:

cd /net/www

Then, run the following command:

php artisan user:resetpw

The command will ask for the username and then for a new password.

Notitie

When typing the new password, nothing will be displayed.

You should now be able to authenticate in the front-end with the new password.

Cases

Overview of the Case administration page. Here it’s possible to create, edit, archive and restore cases.

Cases List

The listview offers some settings and features. The checkboxes can be used to toggle functionality or settings on a case. The columns in the table are:

  • On

    Whether the case is enabled or not. This setting can be toggled on the “Edit Case” page.

  • Backup

    Whether the case will be backed up when backup settings are configured.

  • Spider?

    Enable or disable the spider for this case.

    Pas op

    Do not disable the spider during indexing.

  • Arch.

    Whether the case is archived or not.

  • Class.

    Enable or disable the Classification Module.

  • Privacy

    Enable or disable the Privacy module.

  • Users

    Name of the Active Directory group to grant “User”-level access to this case.

  • Managers

    Name of the Active Directory group to grant “Manager”-level access to this case.

  • Actions
    • Yellow boxes button: Click this button to archive the case.

    • Blue paper button: Edit this case.

    • Red trashbin button: Delete this case.

      Notitie

      Last case cannot be deleted.

Adding a case

From this page, it’s possible to create a new case on the appliance. Simply click the “Add Case” button. You will be redirected to the following page:

Here you can fill in the following details:

  • Name

    Name of the case.

  • Description

    Description of the case.

  • Enabled

    Whether the case is enabled or not. If unchecked, the case will not show up for users and managers.

  • AD Group for users

    The Active Directory group that is used to grant users access to this case with “User”-level. When Active Directory integration has not been activated, “No AD connection” will be shown here.

  • AD Group for managers

    The Active Directory group that is used to grant users access to this case with “Manager”-level. When Active Directory integration has not been activated, “No AD connection” will be shown here.

When all details are filled in, click the “Create” button. A new case will be created. This may take several seconds.

Editing a case

To edit a case, navigate to the “Cases List” and click the blue paper icon in the “Actions” Column. The following page will open:

From here, it’s possible to edit the case. See “Adding a case” for details about the fields. Click “Save Changes” when the desired changes have been made.

This page also shows the users that have access to this case and the created collections in this case.

Archiving a case

To archive a case, navigate to the “Cases List” and click the yellow boxes icon in the “Actions” column. INDICA will now automatically archive this case. The case will be disabled and cannot be accessed anymore.

When the archiving is done, the case will be displayed in the “Cases Archive list”.

Notitie

This list displayes the archived cases by their Case ID as this is unique for every case.

From this list, the archived case can be downloaded in a .tar.gz format. The downloaded file will contain everything that is needed to later restore the case.

If the archived case is no longer needed, it can be deleted by clicking the red trashbin icon.

Pas op

This action is irreversible and the data is lost permanently.

Restoring a case

INDICA offers the possibility to restore a previously archived case. To do this, navigate to the “Cases List” page. Here a section is shown where you can upload INDICA .tar.gz files.

Click the “Choose File” button to select the .tar.gz archive. After choosing the correct file, the upload will start. When the upload is done, click the “Submit” button to restore the case from the archive. The case will now be restored and displayed in the “Cases List”.

Deleting a case

Deleting a case is done from the “Cases List” page. In the “Actions” column, a red trashbin icon is displayed. When that icon is clicked, a confirmation box will pop up. This is to prohibit accidental deletion.

Pas op

Deletion of a case is permanent and irreversible. This action cannot be undone.

There must always be one case in the system. The last case cannot be deleted.

Networking

Overview of the Networking page.

On this page, several settings regarding networking can be configured:

  • Schedule bandwith throttling

    Schedule how much bandwith the INDICA appliance may use at certain times/days.

  • Network interface

    Basic settings for configuring the network interface

  • Mailer settings

    Connect INDICA to a mail server so it can send out notifications

  • Proxy settings

    Configure a proxy server

  • Zabbix monitoring

    Configure zabbix monitoring

  • SSL Settings

    Configure a Secure Socket Layer certificate for the web front-end.

Schedule bandwith throttling

While indexing, the INDICA appliance can take up quite a bit of network bandwith. To make sure that the infrastructure will not be overloaded, you can schedule the maximum allowed bandwith to be used by the INDICA appliance.

There are two options for scheduling:

  • Daily Schedule

    This schedule will apply every day. It allows you to set a throttle start time and stop time, and the maximum Mbps it may use.

  • Custom Schedule

    This schedule allows you to select the days. It allows you to set a throttle start time and stop time, and the maximum Mbps it may use.

Setting a daily schedule

First, click the “Change schedule” button. You will be presented with the following options:

Then, pick a time for the throttle to start and to stop. Lastly, enter a value for the maximum Mbps the appliance may use.

Click “Save changes” to apply the schedule. The schedule should now be active.

Setting a custom schedule

First, click the “Change schedule” button. You will be presented with the following options:

Now click the days you want the schedule to be active. Then, pick a time for the throttle to start and to stop. Lastly, enter a value for the maximum Mbps the appliance may use.

Click “Save changes” to apply the schedule. The schedule should now be active.

Network interface

In most cases, the network will be configured by DHCP. In case that is not true in your setup, this panel allows you to set the correct network settings.

Here you can configure the following settings:

  • IP address

  • Subnetmask

  • Gateway

  • DNS Nameserver

Notitie

When the checkbox “Set by DHCP?” is checked, these settings cannot be changed.

Mailer settings

Here you can configure INDICA to connect to a mail server so it can send out emails.

It needs the following information:

  • Mail address

  • SMTP server

  • SMTP port

  • Mail user

  • Mail password

After entering the correct information, click “Save Changes” to apply the changes.

Proxy settings

This panel contains the Proxy settings.

Notitie

To use credentials, enter the settings in the following format:

http(s)://[user]:[password]@[proxyserver]:[port]

Zabbix monitoring

Here you can enter the settings for Zabbix monitoring.

It needs:

  • Zabbix Server (IP address)

  • Zabbix Hostname (usually ‘indica’)

SSL Settings

SSL Settings allows you to use SSL to secure the client-server traffic of the web-based frontend.

SSL can be set up in three ways:

  • Use a self-signed certificate

  • Submit a CSR (Certificate Signing Request)

  • Upload own certificate and keyfiles

Use a self-signed certificate

When clicking the button “New Self-Signed Certificate”, you will be prompted to fill in some information:

After filling in the fields, click “Submit”. The certificate is now active.

Belangrijk

Modern browsers may still notify to the user that the connection may not be secure when a self-signed certificate is used.

Submitting a CSR

When clicking the button “New CSR”, you will be prompted to fill in some information:

After filling in the fields, click “Submit”.

Upload own certificate and keyfiles

INDICA also provides the option to use your organisation’s own certificate and keyfiles. They can be uploaded after clicking the “Upload files” button. It wil then prompt the following files:

Upload the corresponding files, and then click “Submit” to activate.

Security

Security Settings allows different ways to authenticate users. It is possible to setup an integration with an Active Directory (AD) and OpenLDAP, as well as Single Sign On (SSO). There is also a setting to disable reading the ACL from shares. This means that every user in INDICA can see all documents, regardless of Whether or not they are allowed to see the document on the original data source.

Enabling Active Directory integration

Active Directory integration allows for user and group management in the existing AD/LDAP environment. To make use of it, an account which can be used to ‘bind’ to the AD/LDAP is needed. Then, fill in the following information:

  • Check the ‘Use AD integration’ box

  • Enter the hostname or IP. Usually, IP works better due to resolving the name.

  • Enter the correct port

  • Enter the Workgroup Name (NETBIOS)

  • Enter the Domain Name (realm)

  • Enter the Bind Username (with NETBIOS/realm notation)

  • Enter the password of the Bind User

  • (optional; if needed) Check the box ‘Authenticate against AD Forest’

Then, click on ‘Test Connection’. If everything is setup and entered correctly, INDICA should report back all the AD groups it can find. If this is the case, click ‘Save Changes’ to store and apply the settings.

Now, the existing AD structure can be used to map existing AD groups to INDICA cases.

This is done by setting up two groups per INDICA case:

  • A User-level access group.

  • A Manager-level access group.

These two groups can then be linked to the corresponding INDICA case in the Case Settings. When all groups are set up, users can be added to or removed from the group at will. Edits to the groups in the AD/LDAP environment will be reflected in INDICA immediately.

Enabling Single Sign-on

Single Sign-on(SSO) allows users to access the INDICA interface without having to bother with a username and password. INDICA will automatically sign in users if they are already authenticated.

SSO needs the following information:

  • Domain Controller

  • Domain Controller 2 (optional)

  • Workgroup Name (NETBIOS)

  • Domain Name (realm)

  • Second UPN Realm (only enter if specifically needed)

  • Appliance Name

  • Join Account (only used once)

  • Join Password (only used once)

When using SSO, some actions may be required on different parts of the infrastructure (outside the INDICA appliance). Use the following list to make sure everything is set-up properly:

  • NTP service available on DC1.

  • Appliance name needs to be added to DNS.

  • Join account has sufficient rights.

When everything is set-up properly, users should be able to access the INDICA interface without having to authenticate themselves.

Software & Support

The Software & Support section helps managing the current license, software versions, and support connection.

Activation Key

Here you can view and edit the software key that is used to activate your INDICA appliance.

Notitie

Please keep in mind that the keys are not interchangable between appliances, as they are tied to the hardware as well. In case a new appliance needs to be activated, contact INDICA support to assist you.

Software version

This panel allows you to check the current software version.

It shows you the current version number, as well as the version numbers of all the packages as well. It is possible to update packages by hand, and if needed, roll back to previous versions. This can only be done if there was a previous version installed on the appliance.

With the ‘Select package’ option, a package can be uploaded to the appliance. INDICA will automatically recognise the type of package uploaded, and it’s version and add the package to the overview if it has a newer version than currently active.

Clicking the switch in the ‘Previous’ column rolls back the version of active package.

Updates

This panel allows you to toggle automatic updates on or off. You can also specify Whether offline packages should be used or not.

Remote Connection

This option allows appliance administrators to toggle remote connections. The remote connections are used by INDICA engineers to remotely troubleshoot and support your appliance. It is advised to leave this setting turned on.

Here you can also copy the public SSH key of the appliance, and force a remote connection to the INDICA server.

General Settings

This section of the settings allow you to configure a few things:

  • Use internal user DB

    When not connected to an external authentication service, it is possible to use the internal authentication database.

  • Solr Index Node

    Location of the Solr index node. Only to be edited when running in a cluster Be careful, as changing this setting may lead to an unstable/broken cluster

  • Solr Query Node

    Location of the Solr query node. Only to be edited when running in a cluster Be careful, as changing this setting may lead to an unstable/broken cluster

  • Tika Location Full URI

    If Apache Tika is hosted externally, then edit this value to point the indexer to the correct location

  • Enable logging API

    Enable logging API so logging can be used with external programs/services

    Waarschuwing

    This might be a security issue! Case information will be accessible externally

Backup Settings

This page allows you to setup the backup location. It needs the following information:

  • UNC path of the backup location

    Location where INDICA can read and write it’s backups to

  • Backup username

    Username for INDICA to authenticate on the backup location

  • Backup password

    Password of the corresponding user that INDICA can use to authenticate on the backup location

Look and Feel

INDICA allows you to apply your custom Look and Feel to the appliance. This can be done on two levels:

  • Appliance level

    This is configured in the admin interface and applies to the admin section

  • Case level

    This is configured in the case management interface and applies to that case only This allowes for customised look and feel in different cases

The settings allow you to change the following:

  • Application front-end language

    Supported languages: Dutch, English, French, German

  • Logo

    PNG format, 250x50 pixels, max 20kb

  • Fonts, interface and text colors

    Allows changing the colors and fonts of the main interface

  • Privacy fonts and colors

    Allows changing the colors and fonts of the Privacy interface

When hovering the mouse over the color pickers, a preview is shown:

All values can be changed individually, and reset to default if needed.