| name | adobe-express-oauth-authentication |
| description | Implement OAuth 2.0 and authentication flows for Adobe Express add-ons. Use when connecting to cloud providers (Dropbox, OneDrive, Google Drive), managing tokens, storing credentials, or designing login surfaces. |
Adobe Express OAuth and Authentication Skill
This skill guides you through OAuth 2.0 implementation for add-ons, focusing on PKCE flow, token lifecycle, and secure credential storage.
When to Use This Skill
- Implementing OAuth for cloud storage access (Dropbox, Google Drive, OneDrive)
- Designing PKCE flow for add-on iframe runtime
- Planning token storage and refresh strategy
- Validating manifest OAuth permission requirements
- Debugging OAuth callback failures or token expiration issues
Quick Start
Understand PKCE Flow for Add-ons
OAuth 2.0 with PKCE (Proof Key for Code Exchange) is the standard for add-ons:
- User clicks "Connect to [Provider]" button (UI)
- Add-on generates PKCE challenge and redirects user to provider
- User authorizes add-on at provider
- Provider redirects to Adobe's OAuth proxy with authorization code
- Add-on exchanges code + verifier for access token
- Token stored in Client Storage for future requests
Add OAuth Permissions to Manifest
{
"permissions": {
"oauth": [
"www.dropbox.com",
"login.microsoftonline.com",
