Module 8 Cheat Sheet

CONFIGURATION
=============

${foo}
→ application/environment property

vars.foo
→ current Mule event variable


ENVIRONMENTS
============

dev / qa / prod

same artifact
different configuration


SECRETS
=======

Never hardcode

Secure Properties:
![encrypted value]

Access:
${secure::foo}

decryption key:
injected separately


SALESFORCE AUTH
===============

Current Connector 12:

OAuth 2.0
OAuth Client Credentials
OAuth JWT
OAuth SAML
Basic auth in supported scenarios

Old OAuth Username-Password flow:
removed from Connector 12


SECURITY
========

dedicated integration identity
least privilege

object permissions
field-level security
record access

TLS protects transport
OAuth handles identity/access context

Never log:
tokens
passwords
secrets
private keys


DEPLOYMENT MODEL
================

        Mule artifact
             ↓
     ┌───────┼───────┐
     ↓       ↓       ↓
    DEV      QA     PROD
     ↓       ↓       ↓
 separate configuration
 separate credentials

The main sentence to remember is:

“I want one immutable Mule artifact promoted across environments, with endpoints, credentials and secrets injected through environment-specific secure configuration.”

That immediately communicates that you understand both Mule development and production deployment practices.