BookatlasTwo-Day MuleSoft → Salesforce Bootcamp
5 / 18 · Module 8 — Configuration and Security · filtered: cheatsheet← prev⊞ allnext →

8.48Don't print secrets to diagnose configuration

A junior debugging reaction:

logger:
"clientSecret = ${secure::salesforce.clientSecret}"

Absolutely not.

Better:

Salesforce configuration loaded
client ID suffix: ****1234
endpoint: sandbox

if even that information is permitted.

Never debug auth by exposing the secret itself.