Configuration

[plugin:auth_tkt]
use =uibase.lib.auth_tkt:make_plugin
# this is a generic value, it is changed in the appliance RPM
# do not change this value without changing the spec files (uses
# the value in a search and replace sed command)
secret =some browsers enable drag-n-drop only when dataTransfer has data xxxxxxxxxxxxxxxxxxxxx
timeout =7200
reissue_time =300
secure =True

dn:cn=Account Inactivation Policy,dc=searchappliance,dc=com
objectClass:top
objectClass:ldapsubentry
objectClass:extensibleObject
objectClass:accountpolicy
accountInactivityLimit:5184000
cn:Account Inactivation Polic

Admin Tile

The following files are found through the Configuration page in the Admin tile. 

Enabling Search Authentication

You can require users to log in to the search interface. This can protect your critical data from being seen by individuals who have no legitimate reason to access the data. However, if you enable this option, you take on the responsibility of managing user accounts for everyone who needs access to the data.

1. In the Navigation menu, click Configuration, then select search-ui.ini from the menu.
2. Set the require_query_authentication parameter to True. To disable this feature, set the parameter to False.
3. Click save.
4. The ps-search-ui service must be restarted in order for changes to take effect. Contact professional services in order to restart it.

Enabling Collections

Collections allow you to give groups access to documents based on the file path.

1. In the Navigation menu, click Configuration, then select search-ui.ini from the menu.
2. Set the enable_collections parameter to True. To disable this feature, set the parameter to False.
3. Click save.
4. The ps-search-ui service must be restarted in order for changes to take effect. Contact professional services in order to restart it.

Configuring the Usage Logs

The search server saves information on each user as he or she uses the server. Because this information is logged, it is possible to search usage log entries in detail. The searchable logs provide information on who has searched, what has been searched, and when it has been searched. Other collected data includes URLs, clients, HTTP methods, etc.

Turning On and Off Usage Logs

1. Select one of these files from Choose a file:
   • searchserver-ui.ini
   • search-ui.ini
   • admin-portal.ini
2. Scroll down the script until usage_logs = True is found.
3. Make sure it reads True to record usage logs. Change it to False if usage logs should not be recorded; however, not recording logs is not recommended.
4. Repeat steps 1 through 3 until all three files are configured.
5. Click save.

Changing the Usage Log Level

The level settings determine how much information is recorded. By default, the level is set to INFO. The lower the level of tracking is set, the more hits are returned with the usage log. The levels available from lowest to highest priority are DEBUG, INFO, WARNING, ERROR, and CRITICAL. Debug is the lowest level and therefore returns the most hits because it collects all the data from debug to critical. If only critical is chosen, the other four are not searchable.

It is possible to change the level of logs recorded; however, because almost all entries are recorded on the INFO level, the need to change these levels is minimal and should not be done under most circumstances.

Below are steps to change the level of recorded entries:

1. While still in the files above, locate the Logging configuration section.
   

   # Logging configuration
   [loggers]
   keys = root, routes, searchserverui, usage, gunicorn.access
   ...
   [logger_root]
   level = INFO
   handlers = console

   Note:

   Capitalization of the value is important; make sure each level value is in all capital letters.
2. Make all the level changes necessary for each section.
3. Click save.
4. Repeat for each configuration file.