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

Jamie Lee Curtis isn’t just having a moment, she is THE moment.

Ian sent me this clip Jamie Lee Curtis on the Tonight Show with Stephen Colbert. It is phenomenal. I adore her. I resonate with so much with what she describes here. I too am an artist. I too have struggled […]

via Blog – Brad Frost August 12, 2025

Monero faces 51% attack

Monero, a privacy-focused blockchain network, has been undergoing an attempted 51% attack — an existential threat to any blockchain. In the case of a successful 51% attack, where a single entity becomes responsible for 51% or more of…

via Web3 is Going Just Great August 12, 2025

Camp Snap Impressions

I took the Camp Snap out for a test run on Sunday

via Robb Knight • Posts • Atom Feed August 12, 2025

Generated by openring