Security settings page
Repository > General Settings > Security
Page purpose¶
This page makes it possible to manage various security settings, authorising operations performed outside of CCH Tagetik and data processing that does not need CCH Tagetik to be open.
Page fields
Please find below the most important fields.
| Field | Description |
|---|---|
| Security configurations | |
| Enable Web Services | Enables access to the web services offered by CCH Tagetik. Essential in the presence of the Sharepoint module. |
| Enable public REST APIs | Enables public APIs without restarting the application server. Note: if disabled, the system will show the Status 503 error during calls to endpoints. |
| Encrypt .NET (Deprecated) | Encodes data exchanged between the .NET client and the application server. |
| Show server system info. | Sends detailed information to the client, useful in case of errors or issues. The information is also collected when the user is not yet authenticated. |
| Show last login window | When logging in to CCH Tagetik, a pop-up displays the date of the current user’s last login. The information is displayed using the client’s time zone. |
| SSRF Endpoint Check | During creation, it enables validation checks on the URL attribute (or similar) of the Endpoints. Note: only valid for Cloud versions |
| Application server: permitted directories | Allows you to indicate the absolute paths of the directories visible from the Application Server for which it is permitted to read or write files with CCH Tagetik tools. |
| Valid file types | |
| Attached documents: allowed file types | Types of files that can be attached in CCH Tagetik. Note: metacharacters can be used; use commas to separate the extensions. |
| Timeouts | |
| Client socket (min) | Timeout for the socket in read mode for a certain HTTP client. 0: no timeout |
| Idle session timeout (min) | Minutes of inactivity after which the system automatically performs the logout. -1: no automatic logout |
| Data processing (sec) | Timeout for data processing and sub-processing. Once reached, the system stops the current data process or sub-process and sends the message Data processing |
| Query 1 (sec) | Indicates after how many seconds any query that is run during data processing must be aborted. Note: If the value of this field is equal to 0, no timeout will be set. |
| Query 2 (sec) | Waiting time for long data processes before a current query is stopped. |
| Thread Dump | |
| Automatic thread dump in case of lock | Automatically downloads a thread dump locally in case requests are locked out from the application server. If enabled, also specify the time period between two dumps. Default: 60 sec. Note: setting reserved for technical staff. |
| Time after which a request is considered blocked (sec) | Time after which a request is considered blocked if not executed. Default: 30 sec. |
| JVM Heap | |
| Load % to enter critical state | Maximum percentage of old-generation JVM memory occupied. In addition to this value, the system warns when a critical state is reached. |
| Action to take when in critical state | Action required when the memory is in a critical state (see Critical State Memory Manager). - None: no action to be taken - Tracking enabled: no action to be taken. Tracks memory status in application logs. - Prevent new data processing: prevents new data processes from being run, and stops processes that are underway. Data processes that use the most memory will be stopped first and then, where memory usage is the same, the most recent processes will be stopped. - Stop data processing in progress and prevent new data processes using force memory purge of the garbage collector: prevents new data processing and terminates current processes. Data processes that use the most memory will be stopped first and then, where memory usage is the same, the most recent processes will be stopped. If the status remains critical for more than one minute after data processing has been interrupted, the garbage collector will be activated to force a memory clean-up. |
| Other | |
| Number of reruns in case of deadlock | Number of times the system must attempt to rerun a query that has acquired lock status due to an exception, in order to resolve deadlock statuses on the MSSQL Server and Oracle. |
| Query fetch size | Number of records that must be read by a query during block-based reading |