OceanBase
English日本語简体中文
Docs Home
Products
Integrations
Release Notes

Databases

OceanBase DatabaseOceanBase Cloud OceanBase Best Practices

Tools

OceanBase Cloud PlatformOceanBase Migration ServiceOceanBase Developer CenterOceanBase Migration AssessmentOceanBase Admin ToolOceanBase Loader and DumperOceanBase DeployerKubernetes operator for OceanBaseOceanBase Diagnostic Tool OceanBase Binlog Service

Connectors and Middleware

OceanBase Database Proxy OceanBase Connector/C OceanBase Connector/J OceanBase Connector/ODBC OceanBase Connector/NETOceanBase Command-Line Client

Databases

OceanBase DatabaseOceanBase Cloud OceanBase Best Practices

Connectors and Middleware

OceanBase Database Proxy OceanBase Connector/C OceanBase Connector/J OceanBase Connector/ODBC OceanBase Connector/NETOceanBase Command-Line Client

Tools

OceanBase Cloud PlatformOceanBase Migration ServiceOceanBase Developer CenterOceanBase Migration AssessmentOceanBase Admin ToolOceanBase Loader and DumperOceanBase DeployerKubernetes operator for OceanBaseOceanBase Diagnostic Tool OceanBase Binlog Service
OceanBase DatabaseOceanBase Cloud ToolsConnectors and MiddlewareLifecycle Support Policy

OceanBase Deployer

V4.3.0Community Edition
  • What is obd
  • Quick Start
    • Install obd
    • Quick deployment of OceanBase Database
    • Quickly deploy OCP
  • obd Command
    • Quick deployment commands
    • Cluster commands
    • Command groups
    • Image and repository commands
    • Test command groups
    • Tool commands
    • obdiag commands
    • Binlog service commands
    • Hardware commands
    • License commands
    • Password commands
    • Telemetry commands
  • User Guide
    • Usage overview
    • Deploy through GUI
      • Overview
      • Pattern configuration rules
      • Deploy an OceanBase cluster
      • Deploy OCP
      • Deploy OMS
      • Change components
      • Upgrade OCP
      • Upgrade OMS
    • Deploy through CLI
      • Configuration file
      • Component deployment
        • Deploy an OceanBase cluster
        • Deploy seekdb
        • Deploy obconfigserver
        • Deploy OMS
        • Deploy OCP
        • Deploy Alertmanager
        • Deploy obbinlog
        • Deploy oblogproxy
      • Cluster management
        • Physical Standby Database
          • Create a standby tenant
          • Role switching and decoupling
          • Switch the synchronization mode between primary and standby tenants
        • seekdb primary/standby instance
          • Create a standby instance
          • Role switching and decoupling
        • Scale out and component changes
        • Performance test
        • Diagnose a cluster
        • Backup and restore
        • Add a GUI monitoring system to an existing cluster
      • Cluster management
        • Use OCP to take over an OceanBase cluster deployed by obd
        • Take over an OceanBase cluster
      • Component upgrade
        • Upgrade OceanBase Database
        • Upgrade ODP
        • Upgrade OMS
  • Upgrade obd
  • FAQ
  • Error codes
  • Release Notes
    • Version rules
    • V4.3
      • OceanBase Deploy V4.3.0
    • V4.2
      • OceanBase Deployment Tool V4.2.0
    • V4.1
      • OceanBase Deployer V4.1.0
    • V4.0
      • OceanBase Deployer V4.0.0
    • V3.6
      • OceanBase Deployer V3.6.0
    • V3.5
      • OceanBase Deployer V3.5.0
    • V3.4
      • OceanBase Deployer V3.4.0
    • V3.3
      • OceanBase Deployer V3.3.0
    • V3.2
      • OceanBase Deployer V3.2.2
      • OceanBase Deployer V3.2.1
      • OceanBase Deployer V3.2.0
    • V3.1
      • OceanBase Deployer V3.1.2
      • OceanBase Deployer V3.1.1
      • OceanBase Deployer V3.1.0
    • V3.0
      • OceanBase Deployer V3.0.1
      • OceanBase Deployer V3.0.0
    • V2.10
      • OceanBase Deployer V2.10.1
      • OceanBase Deployer V2.10.0
    • V2.9
      • OceanBase Deployer V2.9.2
      • OceanBase Deployer V2.9.1
      • OceanBase Deployer V2.9.0
    • V2.8
      • OceanBase Deployment Tool V2.8.0
    • V2.7
      • OceanBase Deployment Tool V2.7.0
    • V2.6
      • OceanBase Deployment Tool V2.6.2
      • OceanBase Deployment Tool V2.6.1
      • OceanBase Deployment Tool V2.6.0
    • V2.5
      • OceanBase Deployer V2.5.0
    • V2.4
      • OceanBase Deployer V2.4.0
    • V2.3
      • OceanBase Deployment Tool V2.3.1
      • OceanBase Deployer V2.3.0
    • V2.2
      • OceanBase Deployment Tool V2.2.0
    • V2.1
      • OceanBase Deployer V2.1.1
      • OceanBase Deployment Tool V2.1.0
    • V2.0
      • OceanBase Deployment Tool V2.0.1
      • OceanBase Deployment Tool V2.0.0
    • V1.6
      • OceanBase Deployer V1.6.2
      • OceanBase Deployer V1.6.1
      • OceanBase Deployer V1.6.0
    • V1.5
      • OceanBase Deployer V1.5.0
    • V1.4
      • OceanBase Deployer V1.4.0
    • V1.3
      • OceanBase Deployer V1.3.3
      • OceanBase Deployer V1.3.2
      • OceanBase Deployer V1.3.0
    • V1.2
      • OceanBase Deployer V1.2.1
      • OceanBase Deployer V1.2.0
  • Interactive deployment of OceanBase Database Community Edition
  • Deploy a Community Edition cluster using the obd graphical interface
  • Deploy a Community Edition cluster by using an obd configuration file

Download PDF

Document Feedback
  1. Documentation Center
  2. OceanBase Deployer
  3. V4.3.0

Password commands

Last Updated:2026-09-04 08:21:29

obd pwd encrypt
Examples
obd pwd set-epk
Examples

OceanBase Deployer (obd) supports encrypting cluster passwords since V3.2.0. This topic describes the commands related to password encryption. You can specify the -h or --help option in a command to query the help information of its subcommands. You can also specify the -v or --verbose option to query the execution details of a command that returns an error.

Note

These commands apply only to obd. Once password encryption is enabled, all clusters managed by obd will be encrypted, including the current and future new clusters.

obd pwd encrypt

You can run this command to enable or disable password encryption.

obd pwd encrypt [enable | disable]

You can use the enable keyword to enable password encryption. If no passkey has been specified before, you must specify one when you enable this feature. If you have specified a passkey by using the obd pwd set-epk command, you must provide the passkey for verification. When you run the obd cluster display command to view cluster information after password encryption is enabled, the cluster passwords are displayed in ciphertext. To view the passwords in plaintext, you must add the --epk or --encryption-passkey option to the obd cluster display command and enter the passkey.

You can use the disable keyword to disable password encryption. To disable this feature, you must provide the passkey for verification. You can provide the passkey by using the --epk or --encryption-passkey option, or enter it when prompted in the command output.

Examples

  • Enable password encryption

    obd pwd encrypt enable
    

    If no passkey has been configured before, the command output is as follows:

    First time setting the encryption passkey. please enter the encryption passkey:
    Please enter the encryption passkey again:
    First time setting the encryption passkey successful!
    Encrypt password ok
    Trace ID: b96a5f82-0ec2-11f0-8b44-00163e49899d
    If you want to view detailed obd logs, please run: obd display-trace b96a5f82-0ec2-11f0-8b44-00163e49899d
    

    If you run the obd cluster display command to view cluster information after password encryption is enabled, the output is as follows, where the passwords after the -p option are displayed in ciphertext.

    +-------------------------------------------------+
    |                 oceanbase-ce                    |
    +---------------+---------+------+-------+--------+
    | ip            | version | port | zone  | status |
    +---------------+---------+------+-------+--------+
    | 10.10.10.1    | 4.3.5.0 | 2881 | zone1 | ACTIVE |
    +---------------+---------+------+-------+--------+
    obclient -h10.10.10.1 -P2881 -uroot -p'********' -Doceanbase -A
    
    +----------------------------------------------------------------+
    |                           obproxy-ce                           |
    +------------+------+-----------------+-----------------+--------+
    | ip         | port | prometheus_port | rpc_listen_port | status |
    +------------+------+-----------------+-----------------+--------+
    | 10.10.10.2 | 2883 | 2884            | 2885            | active |
    +------------+------+-----------------+-----------------+--------+
    obclient -h10.10.10.2 -P2883 -uroot@proxysys -p'********' -Doceanbase -A
    
  • Disable password encryption

    obd pwd encrypt disable --epk=******
    

obd pwd set-epk

You can run this command to specify a passkey or change the passkey.

obd pwd set-epk <new decryption passkey>

The following table describes the options in the command.

Option
Required
Data type
Default value
Description
-c/--current-passkey No string N/A If you have specified a passkey in obd, you must use this option to provide the passkey for verification.
-f/--force No bool N/A If you forget the existing passkey, you can add the -f or --force option to the command to forcibly change the passkey. To do so, you require a user account with sudo privileges and the corresponding password.

Examples

  • Specify a passkey

    obd pwd set-epk 12345
    

    Here is an example of setting the passkey to 12345. If the output is as follows, the passkey is successfully set. If you run the obd pwd encrypt enable command to enable password encryption, you must provide the passkey specified here for verification.

  • Change the passkey

    obd pwd set-epk 123 -c 12345
    

    Here is an example of changing the passkey from 12345 to 123. If the output is as follows, the passkey is successfully changed.

    Check encryption passkey.
    Update encryption passkey successful.
    Trace ID: fb5e2608-0ec2-11f0-a28b-00163e49899d
    If you want to view detailed obd logs, please run: obd display-trace fb5e2608-0ec2-11f0-a28b-00163e49899d
    
  • Forcibly change the passkey

    obd pwd set-epk 123 -f
    

    Here is an example of forcibly changing the passkey to 123. The output is as follows:

    Please input username with sudo privileges. (default: root):
    please input root password:
    Update encryption passkey successful.
    Trace ID: 4f3d41f0-0ec3-11f0-919b-00163e49899d
    If you want to view detailed obd logs, please run: obd display-trace 4f3d41f0-0ec3-11f0-919b-00163e49899d
    

Previous topic

License commands
Last

Next topic

Telemetry commands
Next
on this page
obd pwd encrypt
Examples
obd pwd set-epk
Examples