General Settings
Access the General Settings screen by following Management → System Settings → General Settings. Click the Apply Changes button to save your changes.
An image containing the General Settings screen is shown below:
General Settings Configuration
The fields used for General Settings configuration are shown in the table below:
| Field | Description |
|---|---|
| API Root Context | Field where the Root Context required for API Proxy access is entered. Can only be left as /. Default value: apigateway/ |
| Enable the management of Kubernetes Namespace and Resources with Apinizer (Enable the management of Kubernetes Namespace and Resources with Apinizer) | If this setting is on (default value); All Namespace, Deployment and Service information required for Gateway and Cache Servers are created using the information that Apinizer defines as standard through the API Manager screen, and only Kubernetes definitions allowed through API Manager are made. Update etc. operations are performed through API Manager. If this setting is off; All Namespace, Deployment and Service information required for Gateway and Cache Servers are created using the information that Apinizer defines as standard through the API Manager screen, and only Kubernetes definitions allowed through API Manager are made. Update etc. operations are performed through API Manager. |
| Define your API Integration (Task Flow) Module (Define your API Integration (Task Flow) Module) | The URL address used to access the API Integration (Task Flow) Module from API Manager. This field connects the API integration module with API Manager. |
| Enable Quick Test on API Traffic Log Records (Enable Quick Test on API Traffic Log Records) | If this setting is on (default value); The feature that allows you to make requests again with the request message sent by the client on the API Traffic logs page is enabled. |
| Enable API Traffic Log Details (Enable API Traffic Log Details) | If this setting is on (default value); Detailed view, JSON view and download buttons are displayed on the API Traffic logs page. When disabled, users cannot access detailed log information, JSON view or download log records. |
| Enable Management APIs (Enable Management APIs) | When this option is enabled (enabled by default); You can perform many operations without needing the screen application with Management APIs, and integrate Apinizer into your DevOps environment. |
| Multi Login Settings (Multi Login Settings) | This setting is activated to allow users to log in from different locations and different tabs of their browsers. |
| Enable Hostname Verification For Secure Connections (Enable Hostname Verification For Secure Connections) | If enabled, it checks the common name (CN) and subject alternative names (SANs) of the server certificate to ensure that the hostname matches in SSL/TLS Connections, otherwise hostname verification is disabled in SSL/TLS connections. |
| Navbar Color (Navbar Color) | Apinizer navbar color can be determined according to the hex code entered here. This especially facilitates distinguishing environments for those using multiple Apinizer Management Consoles. |
| Audit Log — record Management Console requests | Off by default. When turned on, every write operation (HTTP POST) sent to the Management Console screens, the Management APIs, APIops, and the API Portal's management backend is additionally recorded as a Manager Request audit event — its path, HTTP method, outcome, and duration, but never its request body, query string, or authentication headers. See Audit Records for details. This switch stays on this page, and is also shown on the Audit row of the SIEM & Log Forwarding page. |
Password Policy
These settings apply only to users whose password Apinizer stores and verifies directly (User Login Type: Database). Users who sign in through an LDAP directory are authenticated there, so this policy does not apply to them.
Every default reproduces the fixed rule Apinizer enforced before this section existed — 8 to 50 characters, drawn from at least 3 of the 4 character types — so an installation that upgrades to this version behaves exactly as before until an administrator turns on a stricter rule.
| Field | Default | Meaning |
|---|---|---|
| Minimum Password Length | 8 | The shortest password a user may set. |
| Maximum Password Length | 50 | The longest password a user may set. |
| Minimum Number of Character Types | 3 | How many of the four character types below (uppercase letter, lowercase letter, digit, special character) a password must contain, independently of which ones are individually required below. |
| Uppercase letter is required | Off | When on, a password must always contain an uppercase letter, regardless of the minimum above. |
| Lowercase letter is required | Off | When on, a password must always contain a lowercase letter, regardless of the minimum above. |
| Digit is required | Off | When on, a password must always contain a digit, regardless of the minimum above. |
| Special character is required | Off | When on, a password must always contain a special character, regardless of the minimum above. |
| Password Validity Period (days) | 0 (never expires) | A password older than this many days must be changed at the next sign-in. 0 disables expiry. |
| Expiry Warning Period (days) | 7 | How many days before expiry a user is warned at sign-in. Only applies when a validity period is set. |
| Password History Size | 0 (disabled) | A user cannot reuse this many of their most recent passwords, counting the one currently in use. 0 disables the check. |
| Force Password Change After Administrator Reset | Off | When on, a user whose password was set by an administrator — at creation or on a later reset — must choose a new one at their next sign-in. Does not apply when an administrator changes their own password. |
Turning on the Password Validity Period does not expire existing users immediately. On upgrade, every existing database user's password age is stamped as of the upgrade itself, so the countdown only starts from there rather than from an unknown date in the past.
See Users for how these rules are enforced when a password is created or changed, and how a required or expired password change is handled at sign-in.
Log recipients (application, token, audit and login logs) and the local storage switches have moved to the SIEM & Log Forwarding page. Destinations, per-stream rules, privacy and size policies are managed there, and that page is now the single source for these settings — values sent for them through this screen, the Management APIs, APIops or a configuration import are ignored.
The "Enable logging disabled fields when blocked" and "Enable logging disabled fields on failure" toggles previously located under General Settings have been removed. This behavior is now managed per connector; see Adding Log Connectors.
Settings such as Captcha, session timeout, SOAP sample generation, deployment history and correlation ID are managed from the System Settings and Limits page.