System General Settings

On this screen, access address definition for API Proxies on an application basis, sending API Traffic Logs to the Connector, Captcha and Idle timeout settings, application and token log settings are made.

The General Settings screen is accessed by going to Administration → System Settings → General Settings.

Click the Apply Changes button to save your changes.

The fields used for the General Settings configuration are shown in the table below.

Field	Description
Apinizer Root Context	This is the field where Root Context required for accessing API Proxy is entered. It can only be left as /. Default value: apigateway/.
Kubernetes Namespace and Resources are managed with Apinizer	If this setting is enabled (default); All of the Namespace, Deployment and Service information required for Gateway and Cache Servers are created by using the information defined by apinizer as standard on the API Manager screen, and only allowed kubernetes definitions via API Manager are made. Updates etc. are done via API Manager. If this settings is disabled; All Namespace, Deployment and Service information required for Gateway and Cache Servers are created by using the information defined by apinizer as standard on the API Manager screen, and only allowed kubernetes definitions are made through API Manager. Updates etc are done via API Manager.
Enable sending API Traffic Logs to Connector in case of failure in response even if log settings are disabled	When this option is enabled (enabled by default); Even if the logs of the relevant API Proxy are closed, in case of errors, the entire request and response are sent to the relevant API Traffic Connector and Connectors. If you want to completely stop logging of API Traffic, this option will be disabled and with it the following fields/menus will be closed completely: All jobs related to analytics Elasticsearch field and display in Environment Analytics menus API Proxy's Tracing, API Traffic and Analytics tabs Anomaly Detector by Query in Monitoring menu The Analytics section of the Overview in the Administration menu OAuth2 policy Log tab in the Test Console Token Requests in the Auditing menu Elasticsearch Clusters and Elasticsearch Monitor in the Server Management menu Elasticsearch, Anomaly and Report jobs Dashboard and API Traffic in Portal
Total Incorrect Logins Allowed for Captcha Validation	When logging into the management console, the number of incorrect logins the user has to make before Captcha verification is activated. Its default value is set to 3.
Total Number of Incorrect Logins Allowed with Captcha Verification to Lock Login	The number of false Captcha verifications that can be made is entered to lock user login when logging into the management console. Its default value is set to 7.
Idle Time	It is the time during which the user can log in to the application and remain in the application without taking any active action (click, scroll, etc.) while logging into the management console. It is in seconds. Its default value is set to 235.
Idle Timeout	When the session idle time ends, it is the waiting period of the dialog in which the user is offered the option to Stay or Log Out. It is in seconds. Its default value is set to 5.
Total History Count of API Proxy's Revision	The number of deployment records to be stored in the database for each API Proxy when a deploy or undeploy operation is performed is specified. The deployment history is used on an API Proxy basis for performing rollbacks. Pinned history values are not included in this count. Its default value is set to 6.
Write application logs to the Apinizer configuration database	According to the logging settings in the API Manager application, logs related to the application flow in the application container and are deleted when the relevant container is closed or restarted. With this setting, it is determined whether or not this logged data will be kept in Apinizer's configuration database. If you select this setting on (default value); Relevant logs will be kept in the Apinizer configuration database and can be viewed on the Application Logs page. If you select this setting off; The relevant logs will not be kept in the Apinizer configuration database and will not be viewable on the Application Logs page.
Write application logs to other targets	Regardless of whether the application logs are written to the Apinizer configuration database, a connector selection can be made in this field to send these logs to another application with the help of a specific connector.
Write token logs to the Apinizer configuration database	According to the logging settings in the API Manager application, data flows in the application container and is deleted when the relevant container is closed or restarted. With this setting, it is determined whether or not this logged data will be kept in Apinizer's configuration database. If you select this setting on (default value); Relevant logs will be kept in the Apinizer configuration database and can be viewed on the Application Logs page. If you select this setting off; The relevant logs will not be kept in the Apinizer configuration database and will not be viewable on the Application Logs page.
Write token logs to other targets	Regardless of whether token logs are written to the Apinizer configuration database, a connector selection can be made in this field to send these logs to another application with the help of a specific connector.

If an incorrect entry is made by the specified value to lock the login, the user becomes locked. The user can be unlocked by the System Administrator under the Users menu.