Enabling and Disabling Security Authentication

Constraints

• After security authentication is enabled, you can only view the namespaces that you have the permissions to access on the console.
• After security authentication is enabled, clients without usernames and passwords cannot access Nacos instances. Exercise caution when performing this operation.
• After security authentication is disabled, permissions of each user cannot be controlled. Clients can access Nacos instances without passwords, and all namespaces are displayed on the console. Exercise caution when performing this operation.

Enabling Security Authentication

By default, security authentication is disabled for Nacos engines. You can enable security authentication on the console.

1. Click the target Nacos engine.
2. Choose Permission Control.
3. Click Set Authentication and enable Authenticate Programming Interface.

4. Click OK. After the Nacos engine is updated and the engine status changes from Configuring to Available, security authentication is enabled successfully.

Disabling Security Authentication

If security authentication is no longer required after being enabled for a Nacos engine, you can disable it on the console.

1. Click the target Nacos engine.
2. Choose Permission Control.
3. Click Set Authentication. On the Security Settings page, disable Authenticate Programming Interface.
4. In the displayed dialog box, click OK. When the status of the engine changes to Available, security authentication is disabled.