Skip to content

Fix: Remove sensitive HTTP payload logging from Ruby SDK clients and templates - #33

Open
magqqgq wants to merge 1 commit into
tkhq:mainfrom
magqqgq:magqqgq-patch-1
Open

Fix: Remove sensitive HTTP payload logging from Ruby SDK clients and templates#33
magqqgq wants to merge 1 commit into
tkhq:mainfrom
magqqgq:magqqgq-patch-1

Conversation

@magqqgq

@magqqgq magqqgq commented Aug 21, 2026

Copy link
Copy Markdown

Description

This PR addresses sensitive HTTP payload logging within the ruby-sdk repository.

Vulnerabilities & Security Defects Remediated:

  • Sensitive HTTP Payload Logging (turnkey_client/lib/turnkey_client/api_client.rb, turnkey_client_inputs/templates/api_client.mustache, turnkey_client_inputs/templates/api.mustache): Debug output previously included full request bodies, response bodies, deserialized response data, and response headers. These values could inadvertently expose private keys, signatures, credentials, or other sensitive user data. The API client and its corresponding code-generation templates have been strictly updated to log only non-sensitive transport metadata: the HTTP method, path, operation name, and status code. The templates were updated alongside the client to ensure future regeneration does not reintroduce the defect.

…templates

### Description
This PR addresses sensitive HTTP payload logging within the `ruby-sdk` repository.

**Vulnerabilities & Security Defects Remediated:**
* **Sensitive HTTP Payload Logging (`turnkey_client/lib/turnkey_client/api_client.rb`, `turnkey_client_inputs/templates/api_client.mustache`, `turnkey_client_inputs/templates/api.mustache`):** Debug output previously included full request bodies, response bodies, deserialized response data, and response headers. These values could inadvertently expose private keys, signatures, credentials, or other sensitive user data. The API client and its corresponding code-generation templates have been strictly updated to log only non-sensitive transport metadata: the HTTP method, path, operation name, and status code. The templates were updated alongside the client to ensure future regeneration does not reintroduce the defect.
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.

1 participant