The Vitess 12.0 Documentationmonitoring/stats backends grpc_auth_mode string Which auth plugin implementation to use (eg: static) grpc_auth_mtls_allowed_substrings string List of substrings of at least one of the client certificate names (separated object names -grpc_auth_mode string Which auth plugin implementation to use (eg: static) - grpc_auth_mtls_allowed_substrings string List of substrings of at least one of the client certificate names (separated object names -grpc_auth_mode string Which auth plugin implementation to use (eg: static) - grpc_auth_mtls_allowed_substrings string List of substrings of at least one of the client certificate names (separated0 码力 | 534 页 | 3.32 MB | 1 年前3
The Vitess 7.0 Documentationmonitoring/stats backends grpc_auth_mode string Which auth plugin implementation to use (eg: static) grpc_auth_mtls_allowed_substrings string List of substrings of at least one of the client certificate names (separated object names -grpc_auth_mode string Which auth plugin implementation to use (eg: static) - grpc_auth_mtls_allowed_substrings string List of substrings of at least one of the client certificate names (separated Definition -grpc_auth_mode string Which auth plugin implementation to use (eg: static) - grpc_auth_mtls_allowed_substrings string List of substrings of at least one of the client certificate names (separated0 码力 | 254 页 | 949.63 KB | 1 年前3
The Vitess 8.0 Documentationmonitoring/stats backends grpc_auth_mode string Which auth plugin implementation to use (eg: static) grpc_auth_mtls_allowed_substrings string List of substrings of at least one of the client certificate names (separated object names -grpc_auth_mode string Which auth plugin implementation to use (eg: static) - grpc_auth_mtls_allowed_substrings string List of substrings of at least one of the client certificate names (separated object names -grpc_auth_mode string Which auth plugin implementation to use (eg: static) - grpc_auth_mtls_allowed_substrings string List of substrings of at least one of the client certificate names (separated0 码力 | 331 页 | 1.35 MB | 1 年前3
The Vitess 9.0 Documentationmonitoring/stats backends grpc_auth_mode string Which auth plugin implementation to use (eg: static) grpc_auth_mtls_allowed_substrings string List of substrings of at least one of the client certificate names (separated object names -grpc_auth_mode string Which auth plugin implementation to use (eg: static) - grpc_auth_mtls_allowed_substrings string List of substrings of at least one of the client certificate names (separated object names -grpc_auth_mode string Which auth plugin implementation to use (eg: static) - grpc_auth_mtls_allowed_substrings string List of substrings of at least one of the client certificate names (separated0 码力 | 417 页 | 2.96 MB | 1 年前3
The Vitess 11.0 Documentationmonitoring/stats backends grpc_auth_mode string Which auth plugin implementation to use (eg: static) grpc_auth_mtls_allowed_substrings string List of substrings of at least one of the client certificate names (separated object names -grpc_auth_mode string Which auth plugin implementation to use (eg: static) -grpc_auth_mtls_allowed_substrings string List of substrings of at least one of the client certificate names (separated object names -grpc_auth_mode string Which auth plugin implementation to use (eg: static) - grpc_auth_mtls_allowed_substrings string List of substrings of at least one of the client certificate names (separated0 码力 | 481 页 | 3.14 MB | 1 年前3
The Vitess 10.0 Documentation
monitoring/stats backends grpc_auth_mode string Which auth plugin implementation to use (eg: static) grpc_auth_mtls_allowed_substrings string List of substrings of at least one of the client certificate names (separated object names -grpc_auth_mode string Which auth plugin implementation to use (eg: static) - grpc_auth_mtls_allowed_substrings string List of substrings of at least one of the client certificate names (separated object names -grpc_auth_mode string Which auth plugin implementation to use (eg: static) - grpc_auth_mtls_allowed_substrings string List of substrings of at least one of the client certificate names (separated0 码力 | 455 页 | 3.07 MB | 1 年前3
TiDB v8.1 Documentationv8.1.0)TiCDC supports client authentication using mutual Transport Layer �→ Security (mTLS) or TiDB username and password. This feature enables �→ CLI or OpenAPI clients to authenticate their client authentication using client certificates, thereby establishing mutual Transport Layer Security (mTLS). Additionally, you can configure authentication based on TiDB username and password. For more information 49 Configuration file Configuration parame- ter Change type Description TiCDC security �→ . �→ mtls Newly added Controls whether to enable the TLS client authenti- cation. The default value is false 0 码力 | 6321 页 | 107.46 MB | 1 年前3
TiDB v8.1 Documentationv8.1.0)TiCDC supports client authentication using mutual Transport Layer �→ Security (mTLS) or TiDB username and password. This feature enables �→ CLI or OpenAPI clients to authenticate their client authentication using client certificates, thereby establishing mutual Transport Layer Security (mTLS). Additionally, you can configure authentication based on TiDB username and password. For more information 52 Configuration file Configuration parame- ter Change type Description TiCDC security �→ . �→ mtls Newly added Controls whether to enable the TLS client authenti- cation. The default value is false 0 码力 | 6479 页 | 108.61 MB | 10 月前3
TiDB v8.1 中文手册pingcap.com/zh/tidb/v8.1/ticdc-client-authentication"> �→ 客户端鉴权(从 v8.1.0 开始引入)TiCDC 支持使用 mTLS(双向传输层安全性协议)或 TiDB 用户名密码进行客户端鉴权。 �→ 该功能允许命令行工具或 OpenAPI 客户端验证与 TiCDC 的连接。 2.2.1 功能详情 2.2.1 @CharlesCheung96 在 v8.1.0 中,当使用 TiCDC CLI 或 OpenAPI 时,TiCDC 支持客户端鉴权。你可以配置 TiCDC 要求客户端使用证 书进行鉴权,以实现 mTLS(双向传输层安全性协议)。此外,你还可以使用 TiDB 用户名密码进行客户端 鉴权。 更多信息,请参考用户文档。 37 2.2.2 兼容性变更 注意: 以下为从 v8.0.0 升级至当前版本 TiCDC security.client-user- �→ required 新增 控制是否使用 TiDB 的用户名和密码进行客 户端鉴权,默认值为 false。 TiCDC security.mtls 新增 控制是否开启 TLS 客户端鉴权,默认值为 false。 TiCDC sink.debezium.output- �→ old-value 新增 控制是否输出行数据更改前的值。默认值0 码力 | 4807 页 | 101.31 MB | 1 年前3
TiDB v8.5 DocumentationPulsar �→ enables the mTLS authentication. auth-tls-certificate-path="/data/pulsar/certificate" #### The private key path on the client, which is required when Pulsar �→ enables the mTLS authentication. trusted certificate file of the Pulsar TLS �→ authentication, which is required when Pulsar enables the mTLS �→ authentication or TLS encrypted transmission. tls-trust-certs-file-path="/data/pulsar/tls-trust-certs-file" which will be read from the TiCDC �→ server. token-from-file="/data/pulsar/token-file.txt" 945 • mTLS authentication Sink URI: --sink-uri="pulsar+ssl://127.0.0.1:6651/persistent://public/default/ �→0 码力 | 6730 页 | 111.36 MB | 10 月前3
共 36 条
- 1
- 2
- 3
- 4













