Files
Raúl MarínandClaude Fable 5 d7df9005f4 Gate the AWS profile credentials provider behind use_environment_credentials
`ProfileConfigFileAWSCredentialsProvider` was appended to the provider chain
unconditionally, so a URL-only named collection (which defaults
`use_environment_credentials` to 0) would still sign with the server's
`AWS_SHARED_CREDENTIALS_FILE` profile once a trusted session enabled
`s3_allow_server_credentials_in_user_queries`, contradicting the anonymous
default. The AWS config/credentials file is a server-ambient credential source
like the environment and IMDS providers, so it now sits inside the
`use_environment_credentials` block; with the setting disabled the chain stays
empty and the request goes out unsigned.

Add a regression: with a server profile file and the override enabled, a
URL-only named collection stays anonymous, while
`use_environment_credentials = 1` remains the explicit opt-in.

Co-Authored-By: Claude Fable 5 <[email protected]>
2026-06-12 16:17:04 +02:00

8 lines
152 B
XML

<clickhouse>
<users>
<default>
<named_collection_admin>1</named_collection_admin>
</default>
</users>
</clickhouse>