[feature] SC-166737/improve app proxy security by restricting where token replacements can go #65
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 pull request introduces a new
settingsInjectionconfiguration to themanifest.jsonfile, enhancing how sensitive credentials and tokens are mapped to HTTP request headers and body fields. This change improves the flexibility and security of API integrations by explicitly defining how settings are injected into requests.Settings injection for API requests:
settingsInjectionobject to the API configuration, specifying howclient_idandclient_secretare injected into theAuthorizationheader, and howglobal_access_tokenis injected into both the request body (refresh_token) and thexero-tenant-idheader.