System General Settings
On this screen, settings are made to define access addresses for API Proxies on an application basis and to keep indexes in the database when access to Elasticsearch server is not possible, and Captcha and Idle timeout.
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.
|Apinizer Root Context||This is the field where Root Context required for accessing API Proxy is entered.|
|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.
|API Traffic and API Analytics are managed with Apinizer|
If it is activated; Apinizer manages API Traffic and Analytics data. If this value is active, it indicates that API Traffic and Analytics data is managed using Apinizer Elastichsearch.
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:
|Total Incorrect Logins Allowed for Captcha Validation|
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 times how many false Captcha validations can be made to lock user login. Its default value is set to 7.|
|Idle Time||The length of time the user can log in and stay in the application without taking any active action. (click, scrolls etc.)|
|Idle Timeout||When the Idle time is over, it is the waiting time of the dialog in which the user is presented with Stay or Log Out options.|
|Total History of API Proxy's Update Information||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.|
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.