Productivity / Enterprise
Adobe OAuth
Adobe IMS user authentication is product- and project-specific; APIs define their own scopes, approval rules, and production promotion requirements.
Manual / specialised flowProvider docs
What this workflow can do
- Manual provider checklist
- Provider-specific inputs
- Generic OAuth form
Before starting
- Adobe Developer Console project and product API
- clientId and client authentication credential
- redirectUri pattern
- product scopes plus optional offline_access
- authorization code
Result handling
- Use the checklist to complete provider-specific setup outside the generic form.
- Anonymous OAuth Hub workflows do not store secrets, tokens, or provider payloads.
- 01UnderstandReview why this provider needs a specialized setup path.
- 02CollectGather the required provider-specific fields.
- 03Run setupComplete the provider flow outside the generic OAuth form.
- 04ValidateUse the checklist to confirm token and metadata handling.
Specialised flow
Manual provider setup
Adobe IMS user authentication is product- and project-specific; APIs define their own scopes, approval rules, and production promotion requirements.
Required inputs
- Adobe Developer Console project and product API
- clientId and client authentication credential
- redirectUri pattern
- product scopes plus optional offline_access
- authorization code
Troubleshooting
- Credentials begin in Development mode and some Adobe APIs require review before company or school accounts can authorize.
- Request offline_access only when the selected Adobe API permits refresh tokens.
Provider checklist
- Select the Adobe product API before choosing scopes or endpoints.
- Create User Authentication credentials in the Developer Console project.
- Use Adobe IMS authorization and token endpoints documented for that credential.
- Validate the returned token against a low-risk endpoint from the selected product API.