By rajeshreeputra on
Change record status:
Published (View all published change records)
Project:
Introduced in branch:
1.1.x
Introduced in version:
1.1.8
Issue links:
Description:
What Changed
Acquia DAM has simplified site authentication by switching to API token-based authentication. The connection form now displays the current authentication status and uses long-lived API access tokens instead of OAuth for site registration.
Key changes:
- API token authentication - Site connection now uses Acquia DAM API access tokens
- Connection status display - Shows authenticated user and connection state
- No site disconnect - Sites remain permanently connected; update tokens instead of disconnecting
- OAuth retained for users - Individual user authentication still uses OAuth
How to Connect
- Generate an API access token in Acquia DAM (documentation)
- Navigate to
/admin/config/acquia_dam - Enter DAM Domain Name and API Access Token
- Click "Authenticate Site"
Connection status displayed:
- ✓ Success: "Site is authenticated with Acquia DAM using user: [username]"
- ✗ Failed: "Site authentication failed, please update access token"
Field Behavior
- Domain and token fields are disabled (greyed out) when successfully connected
- To update credentials: click "Disconnect Site" first, then re-authenticate
- Connection status updates immediately after authentication
For Existing Sites
- Current OAuth connections continue to work
- No immediate action required
- Recommended: Migrate to API token for better stability
Benefits
✅ More reliable - Eliminates OAuth-related connection issues
✅ Clearer status - Shows authenticated username and connection state
✅ Simpler setup - Single API token replaces OAuth flow
✅ Permanent connections - Sites stay connected to DAM
✅ Better troubleshooting - Connection failures clearly indicated
Impacts:
Site builders, administrators, editors