You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Fix code scanning alert: Clear-text logging of sensitive information (#27)
Address security issue identified in:
https://github.com/jpstroop/fitbit-client-python/security/code-scanning/8
- Add docs/SECURITY.md with comprehensive guidance on debug mode security
- Add explicit security warnings to debug output in _base.py
- Update docstrings in debug-related methods to highlight security risks
Debug mode intentionally includes OAuth tokens for troubleshooting, but
now includes proper documentation and warnings about secure usage.
Copy file name to clipboardExpand all lines: docs/DEVELOPMENT.md
+12-1Lines changed: 12 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -195,10 +195,14 @@ All resource mocks are in the root [conftest.py](tests/conftest.py).
195
195
196
196
### Response Mocking
197
197
198
+
# \<<\<<\<<< Updated upstream The test suite uses the `mock_response_factory` fixture from `tests/conftest.py` to create consistent, configurable mock responses. This is the required pattern for all tests that need to mock HTTP responses.
199
+
198
200
The test suite uses the `mock_response_factory` fixture from `tests/conftest.py`
199
201
to create consistent, configurable mock responses. This is the required pattern
# \<<\<<\<<< Updated upstream For tests that only need to verify parameter validation or endpoint construction (not response handling), it's acceptable to use the following alternative pattern:
261
+
256
262
For tests that only need to verify parameter validation or endpoint construction
257
263
(not response handling), it's acceptable to use the following alternative
This approach provides a clean, standardized way to create mock responses with
278
+
# This approach provides a clean, standardized way to create mock responses with \<<\<<\<<< Updated upstream the desired status code, data, and headers. All test files must use one of these patterns.
279
+
271
280
the desired status code, data, and headers. All test files must use one of these
272
281
patterns.
273
282
283
+
> > > > > > > Stashed changes
284
+
274
285
## OAuth Callback Implementation
275
286
276
287
The OAuth callback mechanism is implemented using two main classes:
0 commit comments