| name | adobe-security-basics |
| description | Apply Adobe security best practices for OAuth credentials, secret rotation,
I/O Events webhook signature verification, and least-privilege scoping.
Use when securing API credentials, implementing webhook validation,
or auditing Adobe security configuration.
Trigger with phrases like "adobe security", "adobe secrets",
"secure adobe", "adobe credential rotation", "adobe webhook signature".
|
| allowed-tools | Read, Write, Grep |
| version | 1.6.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
| tags | ["saas","design","adobe"] |
| compatibility | Designed for Claude Code |
Adobe Security Basics
Overview
Security best practices for Adobe OAuth Server-to-Server credentials, I/O Events webhook signature verification, and least-privilege access control across Adobe APIs.
Prerequisites
- Adobe Developer Console access
- Understanding of OAuth 2.0 client_credentials flow
- Access to secret management solution (Vault, AWS Secrets Manager, GCP Secret Manager)
Instructions
Step 1: Secure Credential Storage
ADOBE_CLIENT_ID=abc123def456
ADOBE_CLIENT_SECRET=p8_XYZ_your_secret_here
ADOBE_SCOPES=openid,AdobeID,firefly_api
.env
.env.local
.env.*.local
*.pem
*.key
aws secretsmanager create-secret \
--name adobe/production/credentials \
--secret-string '{"client_id":"...","client_secret":"..."}'
echo -n "your-client-secret" | gcloud secrets create adobe-client-secret --data-file=-
vault kv put secret/adobe/prod client_id="..." client_secret="..."
Step 2: Credential Rotation
Adobe OAuth Server-to-Server credentials support multiple client secrets simultaneously, enabling zero-downtime rotation:
aws secretsmanager update-secret \
--secret-id adobe/production/credentials \
--secret-string '{"client_id":"...","client_secret":"NEW_SECRET"}'
curl -X POST 'https://ims-na1.adobelogin.com/ims/token/v3' \
-d "client_id=${ADOBE_CLIENT_ID}&client_secret=${NEW_SECRET}&grant_type=client_credentials&scope="