R1D39 Secrets in Salesforce

| programming | salesforce |

My entire Trailhead journey started because I wanted to write a couple of custom integrations for work. I made a working POC hacking together various bits and pieces of information that I found online, but taking a step back to actually learn how Salesforce works has been really great.

I am ready to make a non-hacky solution to the problem that I initially set out to solve. In order to get this to work though, I need some way to manage secrets within Salesforce so that I can securely store my API authentication token for the third party service that I am integrating with.

Luckily, there is Trailhead module on Secure Secret Storage in Salesforce.

Salesforce offers a feature called Named Credentials which offers a very straightforward way to manage secrets. Specifically those involving authenticating against a third party API.

Rather than hard-coding the value into your code, you can leverage named credentials to store secrets, allowing you to refer to the named credential to access the secret value, as if it were any other variable in your code.
Sadly, this did not seem to work for me because the API I was using expects a token in the URL rather than allowing for basic authentication.

There are a couple other strategies in place for storing secrets, but they seem like overkill for my specific project.

Thank you for reading! Share your thoughts with me on bluesky, mastodon, or via email.

Check out some more stuff to read down below.

Most popular posts this month

Recent Favorite Blog Posts

This is a collection of the last 8 posts that I bookmarked.

Articles from blogs I follow around the net

Pluralistic: AI solipsists and AI cynics (24 Jul 2026)

Today's links AI solipsists and AI cynics: You don't have to believe that AI "works" to believe that it's a good investment. Hey look at this: Delights to delectate. Object permanence: Malware v stolen computer; Industrial material made from old coffee and...

via Pluralistic: Daily links from Cory Doctorow July 24, 2026

Safari and system design, pt. 2

Around the time I was writing about iPhone’s Safari breaking the expected “tap to jump to the top” gesture, a conversation on social media pointed to yet another thing that this tab control does strangely. A typical use of Safari means two groups of sites:...

via Unsung July 23, 2026

Issue 107 – An unserious offer

The crypto industry has spent $200 million to get a bill too corrupt for Democrats to pass and a president too corrupt to sign anything that might meaningfully limit his grift.

via Citation Needed July 23, 2026

Generated by openring