Can TiKV access tokens or keys be configured separately for each prefix?

This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: TiKV访问token或者密钥配置,能否给每一个prefix单独配置

| username: TiDBer_eGoId1dP

[TiDB Usage Environment] Production Environment / Testing / PoC
[TiDB Version]
[Reproduction Path] What operations were performed when the issue occurred
[Encountered Issue: Issue Phenomenon and Impact]
[Resource Configuration] Go to TiDB Dashboard - Cluster Info - Hosts and take a screenshot of this page
[Attachments: Screenshots/Logs/Monitoring]

Using TiKV as the metadata engine for JuiceFS,

juicefs format \
    --storage s3 \
    ... \
    "tikv://,," \

I would like to ask, can a token be configured here, so that only the key can access the metadata protection mechanism?
Additionally, can different tokens be configured for different prefixes? Thanks!

| username: Jellybean | Original post link

Is the usage scenario of TiKV here to work as a distributed KV storage system?

| username: xfworld | Original post link

Only through the TiDB entry configuration can the Token method be supported, and it must be the authentication-related security mode of the MySQL protocol.

Currently, the encryption mode that TiDB can support is used to protect data transmission security, not this kind of Token access protection mode.
For your reference!

Reference documents:

| username: dba远航 | Original post link

TiDB supports encryption mode, but the configuration method may be different.