Don't expose full credentials information in API#83
Merged
sergeychernyshev merged 2 commits intomainfrom Feb 23, 2026
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
startup-api | 44bc8ab | Feb 23 2026, 01:19 AM |
sergeychernyshev
deleted the
82-dont-expose-full-credentials-information-in-api-only-necessary-for-the-ui
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR refactors the credential listing logic to ensure that sensitive information such as access tokens and refresh tokens are not exposed to the UI or the public API.
Key changes:
PublicCredentialSchemato define safe credential fields.UserDO.listCredentialsto filter and return only safe credential data.renderCredentialsListin the Worker to use the new filtered fields.userdo.spec.tsto verify that sensitive fields are correctly filtered out.Closes #82
✨ Assisted by AI: Gemini