Skip to content

[v3-1-test] Add access_key and connection_string to DEFAULT_SENSITIVE_FIELDS (#61580)#61582

Merged
shahar1 merged 1 commit intov3-1-testfrom
backport-6d9d86c-v3-1-test
Feb 7, 2026
Merged

[v3-1-test] Add access_key and connection_string to DEFAULT_SENSITIVE_FIELDS (#61580)#61582
shahar1 merged 1 commit intov3-1-testfrom
backport-6d9d86c-v3-1-test

Conversation

@github-actions
Copy link

@github-actions github-actions bot commented Feb 7, 2026

Azure Blob Storage, Azure File Share, and Azure Data Lake store
connection strings and shared access keys in the connection extra
JSON under keys that were not matched by the existing sensitive field
patterns. This allowed users with read-only Connection permissions
(e.g. Viewer role) to retrieve these secrets in plaintext via the API.

Adding connection_string and access_key to the default set ensures
these values are automatically redacted in API responses and logs.
(cherry picked from commit 6d9d86c)

Co-authored-by: Ankit Chaurasia 8670962+sunank200@users.noreply.github.com

…TIVE_FIELDS (#61580)

Azure Blob Storage, Azure File Share, and Azure Data Lake store
connection strings and shared access keys in the connection `extra`
JSON under keys that were not matched by the existing sensitive field
patterns. This allowed users with read-only Connection permissions
(e.g. Viewer role) to retrieve these secrets in plaintext via the API.

Adding `connection_string` and `access_key` to the default set ensures
these values are automatically redacted in API responses and logs.
(cherry picked from commit 6d9d86c)

Co-authored-by: Ankit Chaurasia <8670962+sunank200@users.noreply.github.com>
@shahar1 shahar1 marked this pull request as ready for review February 7, 2026 09:26
@shahar1 shahar1 merged commit 5b1304e into v3-1-test Feb 7, 2026
47 checks passed
@shahar1 shahar1 deleted the backport-6d9d86c-v3-1-test branch February 7, 2026 09:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants