Obfuscate example tokens and Sentera IDs#10
Merged
Conversation
denisahearn
changed the title
nickb27
reviewed
May 11, 2026
| | Ruby | `$ ruby upsert_images.rb` | `FIELDAGENT_ACCESS_TOKEN=PAmnCNUyosKShN9K1AEflLOw6T7bA2fRTWTg-vL3P5Y FIELDAGENT_SERVER=https://api.sentera.com IMAGES_PATH="../test_files" SURVEY_SENTERA_ID=mjlmmrw_CO_lk07AcmeOrg_CV_deve_773b47acb_240514_160730 FILE_EXT="*.jpeg" SENSOR_TYPE="RGB" ruby upsert_images.rb` | | ||
| | Ruby | `$ ruby upsert_mosaics.rb` | `FIELDAGENT_ACCESS_TOKEN=PAmnCNUyosKShN9K1AEflLOw6T7bA2fRTWTg-vL3P5Y FIELDAGENT_SERVER=https://api.sentera.com FILE_PATH="../test_files/test.tif" SURVEY_SENTERA_ID=mjlmmrw_CO_lk07AcmeOrg_CV_deve_773b47acb_240514_160730 ruby upsert_mosaics.rb` | | ||
| | Ruby | `$ ruby create_ground_scouting_feature_set.rb` | `FIELDAGENT_ACCESS_TOKEN="PAmnCNUyosKShN9K1AEflLOw6T7bA2fRTWTg-vL3P5Y" FIELDAGENT_SERVER="https://api.sentera.com" SURVEY_SENTERA_ID="mjlmmrw_CO_lk07AcmeOrg_CV_deve_773b47acb_240514_160730" NUM_LOCATIONS=20 NUM_ATTACHMENTS_PER_FEATURE=2 WITH_ATTACHMENTS="none,some,all" ATTACHMENTS_PATH="../test_files" ATTACHMENTS_EXT="*.*" WITH_ATTACHMENT_NAME_KEYS=false,true WITH_ATTACHMENT_NAMES=false,true WITH_NOTES="none,some,all" FEATURE_SET_NAME="<Optional name, otherwise generated from inputs>" ruby create_ground_scouting_feature_set.rb` | | ||
| | Ruby | `$ ruby import_feature_set.rb` | `FIELDAGENT_ACCESS_TOKEN=********* FIELDAGENT_SERVER=https://api.sentera.com SURVEY_SENTERA_ID=000000_CO_aaaaXXXXXX_CV_deve_c00000000_000000_000000 GEOMETRY_PATH="../test_files/test.geojson" FILES_PATH="../test_files" FILE_EXT="*.jpeg" ruby import_feature_set.rb` | |
There was a problem hiding this comment.
Do you think even this GUID formatting is giving too much away?
SURVEY_SENTERA_ID=000000_CO_aaaaXXXXXX_CV_deve_c00000000_000000_000000
Contributor
Author
There was a problem hiding this comment.
I changed the placeholder Sentera IDs with <YOUR ID> placeholders
nickb27
approved these changes
May 12, 2026
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
2 participants
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.
REMINDER: This is a public repository.
Why?
We don't want to give the impression that this information is valid and could be exploited
What?
Obfuscate/remove test data that was flagged by a security researcher as potentially sensitive information.
The tokens and IDs that were being included in
README.mdfiles in this repository were generated in a local, ephemeral development environment, and thus were only valid in that environment, but we don't want to give the impression that this information could be used to exploit FieldAgent in any way.Screenshot(s)
JIRA Link
Code Review Strategy
QA Strategy