-
Setup and onboarding
- Explore Adobe Admin Console
- Sign-in and access
-
Licensing
- Licensing overview
- Licensing types
-
Identity and SSO
- Set up identity
- Integrate with Microsoft Entra
- Integrate with Google Sync
- Integrate with other SSO providers
- Troubleshoot
-
Directories, domains, and access
-
Directories and domains
- Create a directory for SAML identity providers
- Verify domain ownership
- Set up domains for directory authentication
- Move domains across directories
- Encrypted and trusted directory domain transfers
- Move directories between Admin Consoles
- Delete directories and domains
- Automatic account creation overview
- Enable automatic account creation
- Automatic federated account creation FAQ
- Domain enforcement
- Directory trusting
-
Directories and domains
-
Settings
- Asset settings
- Manage encryption
-
User management
- Understand user management
- Manage users and groups
- Manage admins
- Manage user roles
- Migrate users
-
Products and entitlements
- Manage products
- Manage product profiles
- Special programs plans
- Manage entitlements
- Manage automatic assignment
- Manage product access
- Manage self-service policies
- Manage app integrations
- Frame.io integration
- Manage product permissions
- Manage storage and assets
-
Manage services
- Configure services
- Adobe Stock
- Custom fonts
- Adobe Asset Link
-
Deploy apps and updates
- Prepare for deployment
- Manage pre-generated packages
- Create packages
- Customize end-user experience
- Deploy packages
- Use third-party deployment tools
-
Manage Shared Device Licensing (SDL)
- Shared Device Licensing overview
- Deploy Shared Device Licensing
- Manage SDL profiles and user access
- Activate shared device licenses
- Use the Shared Device Licensing toolkit
- Recover shared device licenses
- Shared Device Licensing identity FAQ
- Shared Device Licensing deployment FAQ
- Shared Device Licensing access FAQ
- Known issues in Shared Device Licensing
- Adobe Update Server Setup Tool (AUSST)
- Adobe Remote Update Manager (RUM)
- Troubleshoot
- Contracts and renewals
- Reports and logs
-
Get started with Global Admin Console
- Get started
- Manage your organization
- Reports audit
-
Get help
- Support options
-
General troubleshooting
- Microsoft Purview Information Protection support in Acrobat
- Use the Creative Cloud Cleaner tool to fix installation issues
- Fix app launch errors on Shared Device Licensing machines
- Technical support boundaries for virtualized or server-based environments
- Resolve trial and license expired errors
- Migrating to OAuth Server-to-Server Credentials
- Manage device authentication for Creative Cloud and Acrobat Pro
Collect Charles Proxy logs to debug SSO issues in Creative Cloud mobile apps
The logs of the Charles Web Debugging Proxy packet analyzer app let you debug identity issues with Adobe Creative Cloud mobile apps.
Set up Charles Proxy
Set up your computer as a network proxy and connect your mobile device to it.
Install the Charles Root Certificate on your mobile device to enable SSL proxying.
Configure SSL proxying for the Adobe IMS endpoint
Open the app and go to the sign-in screen.
In Charles Proxy, identify the IMS host used by the application.
Go to Proxy > SSL Proxying Settings, and add the identified host (ims-na1.adobelogin.com) with port 443.
You should now be able to see the unencrypted requests for the endpoint.
Enable rewrite
Go to Tools > Rewrite. For general mechanics of the rewrite tool, see Charles's Rewrite documentation.
Configure the rewrite rule to point the app at your local or test IMS instance.
Test the configuration
Open the mobile application.
Navigate to the sign-in screen and verify that you're prompted to sign in with your local IMS instance.
Share logs with Adobe Customer Care
Export the Charles Proxy session and share the resulting log file with your Adobe Customer Care representative to continue troubleshooting.