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 picture below shows the General Settings screen:

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

Field	Description
API 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/.
Enable the management of Kubernetes Namespace and Resources 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 the logs of the relevant API Proxy are turned off and this setting is on (enabled by default), if the status of the policy executed in Apinizer or the message returned from the backend is "Error"; The header, parameter and body of the request and response are still sent to the relevant API Traffic Connectors even though the logging status is turned off. If the status of the message is "block" or "success", the default log setting of the API Proxy is valid. When this setting is off, API Proxy's default log setting takes effect. Example for Message Status: "Error"; In an API Proxy with log settings turned off, Script policy has been added. Requests sent to API Proxy may be receiving errors due to incorrect writing in the script in this policy. In this situation; If this setting is enabled, the header, parameter and body of the request and response are logged, although the log settings are turned off for the API proxy. If this setting is not enabled, only metric information will be logged since the log settings are disabled for API proxy. Example for Message Status: "Block"; In an API Proxy with log settings turned off, a throttling policy has been added. Requests sent to API Proxy receive errors due to exceeding the limit in the throttling policy. In this case, since the status of the message is "block", the API proxy log setting is valid regardless of this setting, and since the API proxy is disabled, the header, parameter and body of the request and response are not logged. The message status being "Error or Block" can be understood from the type of error returned. You can visit this page for more information.
Enable resending requests with the request message sent by the client on the API Traffic logs page (Quick Test)	When this option is enabled (enabled by default); The feature that allows you to make requests again is enabled with the request message sent by the client on the API Traffic logs page.
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.
Navbar Color	Apinizer navbar color can be determined according to the hex code entered here. This makes it easier for those who use more than one Apinizir Management Console to distinguish between environments.
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.
Maximum number of elements to be created in XML	When generating sample XML from WSDL, the maximum number of elements that the XML to be created can have is entered.
The depth number of nested levels of elements to be created in XML	While generating sample XML from WSDL, the number of levels of elements that the XML to be created can have is entered.
Maximum message size of the generated XML in KB	When generating sample XML from WSDL, the maximum message size of the XML to be created is entered.
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 Token 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 Token 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.
Write audit 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 Audit 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 Audit Logs page.
Write audit logs to other targets	Regardless of whether audit 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.