Failed DATA_BACKUP_DEST validation logs the OSS `access_key` at INFO level

Self Checks

• I have read the Contributing Guide.
• This is only for bug report, if you would like to ask a question, please head to Discussions.
• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report, otherwise it will be closed.
• 【中文用户 & Non English User】请使用英语提交，否则会被关闭 ：）
• Please do not modify this template :) and fill in all the required fields.

OceanBase version

OceanBase CE 5.0.2.0, source revision d128661ca4f5b3d167c1928e556d70d2f901baef, Release+ASan.

Self Hosted

Self Hosted (Source)

Environment

Ubuntu 22.04.5 LTS, x86_64, one-zone loopback observer.

Steps to reproduce

As root@sys on a disposable cluster, execute:

ALTER SYSTEM SET DATA_BACKUP_DEST=
  'oss://edbf-sv06?host=127.0.0.1:1&access_id=EDBF_REPORT_ID&access_key=EDBF_REPORT_ACCESS_KEY&unsupported_edbf_option=1'
  TENANT='sys';

The unsupported option forces local validation failure; no object-storage service is contacted. Inspect the new run's rootservice.log; the authoritative raw log is bundled as artifacts/rootservice.log:

INFO [SHARE] ... parse from(
  value=oss://edbf-sv06?host=127.0.0.1:1&access_id=EDBF_REPORT_ID&
        access_key=EDBF_REPORT_ACCESS_KEY&unsupported_edbf_option=1, ...)

The sink is src/share/backup/ob_backup_config.cpp:415:

LOG_INFO("parse from", K(value), K(backup_dest), K(path), K(config_items_));

artifacts.zip

✔️ Expected Behavior

Backup-destination diagnostics should retain the scheme, path, endpoint, and option names while redacting access_key and any other credential-bearing query values.

❌ Actual Behavior

The complete backup destination is written to an INFO log and includes the plaintext synthetic OSS access_key. The observer remains healthy; this is a log-disclosure result, not a crash.