fix: retrieve SF access token via show-access-token for e2e setup#1210
Merged
Conversation
The Salesforce CLI security update (~May 2026) redacts the access token from `sf org display` (returns "[REDACTED] Use 'sf org auth show-access-token' to view"), which broke e2e test setup with 401s. - set-test-constants script and e2e workflow now fetch the token via `sf org auth show-access-token --json` (CI keeps `::add-mask::`). - Mask real tokens (00D prefix) in the script's printed output while still showing placeholder values to aid diagnosis. - Document the CLI requirement in HOW_TO_RUN_TESTS.md. Co-authored-by: Cursor <cursoragent@cursor.com>
tprouvot
added a commit
that referenced
this pull request
Jun 22, 2026
) The Salesforce CLI security update (~May 2026) redacts the access token from `sf org display` (returns "[REDACTED] Use 'sf org auth show-access-token' to view"), which broke e2e test setup with 401s. - set-test-constants script and e2e workflow now fetch the token via `sf org auth show-access-token --json` (CI keeps `::add-mask::`). - Mask real tokens (00D prefix) in the script's printed output while still showing placeholder values to aid diagnosis. - Document the CLI requirement in HOW_TO_RUN_TESTS.md. # Describe your changes ## Issue ticket number and link ## Checklist before requesting a review - [ ] I have **read and understand** the [Contributions section](https://github.com/tprouvot/Salesforce-Inspector-reloaded#contributions) - [ ] My PR relates to an existing issue or feature request and **I discussed it with maintainer** - [ ] I used SLDS style and limit the usage of custom CSS - [ ] I have performed a self-review of my code - [ ] I ran the [unit tests](https://github.com/tprouvot/Salesforce-Inspector-reloaded#unit-tests) and my PR does not break any tests - [ ] I documented the changes I've made on the [CHANGES.md](https://github.com/tprouvot/Salesforce-Inspector-reloaded/blob/master/CHANGES.md) and followed actual conventions - [ ] I added a new section on [how-to.md](https://github.com/tprouvot/Salesforce-Inspector-reloaded/blob/master/docs/how-to.md) (optional) Co-authored-by: Cursor <cursoragent@cursor.com>
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.
The Salesforce CLI security update (~May 2026) redacts the access token from
sf org display(returns "[REDACTED] Use 'sf org auth show-access-token' to view"), which broke e2e test setup with 401s.sf org auth show-access-token --json(CI keeps::add-mask::).Describe your changes
Issue ticket number and link
Checklist before requesting a review