tencent cloud

TDSQL-C for MySQL

Release Notes and Announcements
Release Notes
Product Announcements
Beginner's Guide
Product Introduction
Overview
Strengths
Use Cases
Architecture
Product Specifications
Instance Types
Product Feature List
Database Versions
Regions and AZs
Common Concepts
Use Limits
Suggestions on Usage Specifications
Kernel Features
Kernel Overview
Kernel Version Release Notes
Optimized Kernel Version
Functionality Features
Performance Features
Security Features
Stability Feature
Analysis Engine Features
Inspection and Repair of Kernel Issues
Purchase Guide
Billing Overview
Product Pricing
Creating Cluster
Specification Adjustment Description
Renewal
Payment Overdue
Refund
Change from Pay-as-You-Go to Yearly/Monthly Subscription
Change from Pay-as-You-Go to Serverless Billing
Value-Added Services Billing Overview
Viewing Billing Statements
Getting Started
Database Audit
Overview
Viewing Audit Instance List
Enabling Audit Service
Viewing Audit Logs
Log Shipping
Post-Event Alarm Configuration
Modifying Audit Rule
Modifying Audit Service
Disabling Audit Service
Audit Rule Template
Viewing Audit Task
Authorizing Sub-User to Use Database Audit
Serverless Service
Serverless Introduction
Creating and Managing a Serverless Cluster
Elastic Scaling Management Tool
Serverless Resource Pack
Multi-AZ Deployment
Configuration Change
FAQs
Serverless Cost Estimator
Operation Guide
Operation Overview
Switching Cluster Page View in Console
Database Connection
Instance Management
Configuration Adjustment
Instance Mode Management
Cluster Management
Scaling Instance
Database Proxy
Account Management
Database Management
Database Management Tool
Parameter Configuration
Multi-AZ Deployment
GD
Backup and Restoration
Operation Log
Data Migration
Parallel Query
Columnar Storage Index (CSI)
Analysis Engine
Database Security and Encryption
Monitoring and Alarms
Basic SQL Operations
Connecting to TDSQL-C for MySQL Through SCF
Tag
Practical Tutorial
Classified Protection Practice for Database Audit of TDSQL-C for MySQL
Upgrading Database Version from MySQL 5.7 to 8.0 Through DTS
Usage Instructions for TDSQL-C MySQL
New Version of Console
Implementing Multiple RO Groups with Multiple Database Proxy Connection Addresses
Strengths of Database Proxy
Selecting Billing Mode for Storage Space
Creating Remote Disaster Recovery by DTS
Creating VPC for Cluster
Data Rollback
Solution to High CPU Utilization
How to Authorize Sub-Users to View Monitoring Data
White Paper
Security White Paper
Performance White Paper
Troubleshooting
Connection Issues
Performance Issues
API Documentation
History
Introduction
API Category
Making API Requests
Instance APIs
Multi-Availability Zone APIs
Other APIs
Audit APIs
Database Proxy APIs
Backup and Recovery APIs
Parameter Management APIs
Billing APIs
serverless APIs
Resource Package APIs
Account APIs
Performance Analysis APIs
Data Types
Error Codes
FAQs
Basic Concepts
Purchase and Billing
Compatibility and Format
Connection and Network
Features
Console Operations
Database and Table
Performance and Log
Database Audit
Between TDSQL-C for MySQL and TencentDB for MySQL
Service Agreement
Service Level Agreement
Terms of Service
TDSQL-C Policy
Privacy Policy
Data Privacy and Security Agreement
General References
Standards and Certifications
Glossary
Contact Us

Enabling/Disabling Custom Password Strength Feature

PDF
フォーカスモード
フォントサイズ
最終更新日: 2026-01-29 18:04:30
You can use the custom password strength feature with the root account or a sub-account granted with the corresponding CAM permissions. This document describes how to enable and disable the custom password strength feature.

Version limits

The custom password strength feature is supported by the following versions:
MySQL 5.7 on kernel minor version 2.0.21 or later and 2.1.7 or later.
MySQL 8.0 on kernel minor version 3.1.7.
You can use this feature only after upgrading the kernel to the above versions. For detailed directions, see Upgrading Kernel Minor Version.

Enabling custom password strength feature

1. Log in to the TDSQL-C for MySQL console.
2. Select the region at the top, find the target cluster in the cluster list, and click the cluster ID to enter the cluster management page.
3. On the cluster management page, select Account Management and enable Custom Password Strength on the right.


4. In the pop-up window, click Next to enter the initial settings page.


5. Complete the following settings and click OK. In the initial settings of the custom password strength feature, two scenarios will be displayed for different password strength levels. Scenario 1: The password strength level is MEDIUM.


Parameter
Description
Password Strength Level
You can select
MEDIUM
or
STRONG
as the strength level.
MEDIUM: The feature under this setting will check the length, digits, letters, and symbols.
STRONG: The feature under this setting will check the length, digits, letters, symbols, and non-compliant word dictionary.
Min Number of Uppercase and Lowercase Pair
The minimum number of pairs of uppercase and lowercase letters that the password must contain. For example, if this parameter is set to `2`, the password must contain at least two uppercase letters and two lowercase letters. Default value: `1`. Value range: 1–50.
Min Number of Digits
The minimum number of digits that the password must contain. Default value: `1`. Value range: 1–50.
Min Number of Symbols
The minimum number of special symbols that the password must contain. Default value: `1`. Value range: 1–50.
Min Password Length
The minimum length of the password. Default value: `8`. Value range: 8–256. This parameter equals to the number of digits + number of symbols + 2 * number of letters, and it must be greater than or equal to 8 for security of your password. If the final value after the sum of above parameters is greater than 8, it will be used as the minimum of the range.
Scenario 2: The password strength level is STRONG.



Parameter
Description
Password Strength Level
You can select
MEDIUM
or
STRONG
as the strength level.
MEDIUM: The feature under this setting will check the length, digits, letters, and symbols.
STRONG: The feature under this setting will check the length, digits, letters, symbols, and non-compliant word dictionary.
Min Number of Uppercase and Lowercase Pair
The minimum number of pairs of uppercase and lowercase letters that the password must contain. For example, if this parameter is set to `2`, the password must contain at least two uppercase letters and two lowercase letters. Default value: `1`. Value range: 1–50.
Min Number of Digits
The minimum number of digits that the password must contain. Default value: `1`. Value range: 1–50.
Min Number of Symbols
The minimum number of special symbols that the password must contain. Default value: `1`. Value range: 1–50.
Min Password Length
The minimum length of the password. Default value: `8`. Value range: 8–256. This parameter equals to the number of digits + number of symbols + 2 * number of letters, and it must be greater than or equal to 8 for security of your password. If the final value after the sum of above parameters is greater than 8, it will be used as the minimum of the range.
Non-Compliant Dictionary
If the password strength level is STRONG, this parameter is configurable. You can click Dictionary Settings for configuration. Each non-compliant word can contain 4–100 letters. After configuration, the system will check passwords for non-compliant words during password verification. If any non-compliant word (case-insensitive) is detected, the verification will fail.

Disabling custom password strength feature

1. Log in to the TDSQL-C for MySQL console.
2. Select the region at the top, find the target cluster in the cluster list, and click the cluster ID to enter the cluster management page.
3. On the cluster management page, select Account Management and disable Custom Password Strength on the right.


4. In the pop-up window, click OK.


5. In the pop-up window, you can click Batch Disable to select other clusters with the custom password strength feature enabled and batch disable the feature.
Note:
Once the custom password strength feature is disabled, the parameters you set will be automatically reset to the default value. If you enable the feature again, you need to configure these parameters again.
You can select up to 20 clusters in one batch disablement operation.

Related APIs

API
Description
This API (OpenClusterPasswordComplexity) is used to enable the custom password complexity feature.
This API (DescribeClusterPasswordComplexity) is used to describe the details of cluster password complexity.
This API (CloseClusterPasswordComplexity) is used to disable cluster password complexity.

ヘルプとサポート

この記事はお役に立ちましたか?

フィードバック