Using RBAC Authentication

Concept

An exclusive microservice engine provides two authentication modes: no authentication and RBAC authentication. To use RBAC authentication, ServiceComb Java chassis must be of version 2.1.3 or later. Earlier versions do not support RBAC authentication.

After RBAC authentication is enabled for a microservice engine, all called APIs can be called only after a token is obtained. For details about the authentication process, see RBAC.

Example Configuration

To use RBAC, obtain the username and password from the microservice engine and then add the following configuration to the configuration file:

servicecomb:
  credentials:
    rbac.enabled: true
    acount:
      name: youracountname # Username obtained from the microservice engine.
      password: yourpassword # Password obtained from the microservice engine.
    cipher: default # Returned name of the name() method in the implementation class.

cipher specifies the name of the algorithm used to encrypt the password. By default, the password is stored in plaintext. Similar to the encryption scheme of AK/SK authentication, API org.apache.servicecomb.foundation.auth.Cipher can be used to encrypt passwords for storage.