Frequently asked questions | Google Federation
- Adobe Enterprise & Teams: Administration guide
- Plan your deployment
- Basic concepts
- Deployment Guides
- Deploy Creative Cloud for education
- Set up your organization
- Identity types | Overview
- Set up identity | Overview
- Set up organization with Enterprise ID
- Setup Azure AD federation and sync
- Set up Google Federation and sync
- Set up organization with Microsoft ADFS
- Set up organization for District Portals and LMS
- Set up organization with other Identity providers
- SSO common questions and troubleshooting
- Manage your organization setup
- Manage products and entitlements
- Manage users
- Administrative roles
- User management techniques
- Change user's identity type
- Manage user groups
- Manage directory users
- Manage developers
- Migrate existing users to the Adobe Admin Console
- Migrate user management to the Adobe Admin Console
- Manage products and product profiles
- Manage products
- Manage product profiles for enterprise users
- Manage automatic assignment rules
- Review product requests
- Manage self-service policies
- Manage app integrations
- Manage product permissions in the Admin Console
- Enable/disable services for a product profile
- Single App | Creative Cloud for enterprise
- Optional services
- Manage Shared Device licenses
- Manage users
- Manage storage and assets
- Asset migration
- Reclaim assets from a user
- Student asset migration | EDU only
- Manage services
- Adobe Stock
- Custom fonts
- Adobe Asset Link
- Adobe Acrobat Sign
- Creative Cloud for enterprise - free membership
- Deploy apps and updates
- Create packages
- Customize packages
- Deploy Packages
- Manage updates
- Adobe Update Server Setup Tool (AUSST)
- Adobe Remote Update Manager (RUM)
- Create packages using Creative Cloud Packager (CC 2018 or earlier apps)
- About Creative Cloud Packager
- Creative Cloud Packager release notes
- Application packaging
- Create packages using Creative Cloud Packager
- Create named license packages
- Create packages with device licenses
- Create a license package
- Create packages with serial number licenses
- Packager automation
- Package non-Creative Cloud products
- Edit and save configurations
- Set locale at system level
- Manage your account
- Manage your Teams account
- Assign licenses to a Teams user
- Add products and licenses
- Automated expiration stages for ETLA contracts
- Switching contract types within an existing Adobe Admin Console
- Purchase Request compliance
- Value Incentive Plan (VIP) in China
- VIP Select help
- Reports & logs
- Get help
The document covers common questions encountered while configuring Adobe Admin Console SSO with Google Admin Console and managing Google Sync.
The section answers questions related to authentication with Google federation:
Only Federated ID user accounts are created using the Google federation setup. Learn more about the identity type options here.
The Google federation setup can only provide user management for a primary Console in a primary/trustee Console relationship. Any trustee Consoles can take advantage of single sign-on with the federated directory but must use a separate form of user management (such as CSV manual upload, User Sync Tool, or User Management API).
The list answers questions related to Google Sync:
FirstName, LastName, Username, Email, and Country Code.
Google Sync automates user management for your Admin Console directory. You can easily add Google Sync to any existing federated directory in the Admin Console regardless of its identity provider (IdP). To use Google Sync, you must have your organization’s user data stored within the Google Directory.
If the user is part of the sync and the Federated ID username matches a Google-synced username, then Google Sync takes over and manages the profile. If the user is not a part of the sync, the user is able to authenticate as long as the profile matches with the Google profile information.
No, there are currently no visible event logs available in the Adobe Admin Console to assist with troubleshooting Google sync. However, you can monitor automated user provisioning in the Google admin console.
Google Admin Console controls the provisioning rate. Google Sync automatically adds or removes user licensing based on the user accounts included in the chosen Google directory groups.
No. A directory can associate with only one type of sync setup.
Google Sync does not currently support group syncing from the Google directory. During the setup process, a Google Admin Console administrator will identify the groups in the Google directory that contain users who should receive access to Adobe licensing. Users from these groups will be automatically synced to the Adobe Admin Console in a flat list, appearing as Federated ID accounts in the User tab in the Adobe Admin Console. Once the user accounts are created, the administrator can choose to group users into specific user groups to provide specific access to product licenses for a subset of users.
As an example, your education organization has 5,000 users, including 500 faculty or staff members, 2,000 grade 7 - 12 students, and 2,500 K- 6 grade students. All faculty or staff members and 7- 12 grade students will receive access to Adobe Express, a shared device license for access in the lab environment, and a take-home Creative Clouds All Apps license, while K-6 students only have access to Adobe Express and Shared Device License entitlements. The sync process would go as follows:
- Set up Google Sync with production directory and domains.
- Choose directory groups in Google directory that contain faculty or staff and all student users.
- Run initial sync for 5,000 users to Adobe Admin Console (this takes about 2 hrs to complete).
- In the Adobe Admin Console, create a user group named All Apps Creative Cloud.
- Assign the All Apps CC user group to the All Apps CC product profile. This will automatically license any user of the All Apps CC user group with an All Apps CC license.
- Use Edit Users by CSV option in the Users tab to download the current user list and curate which users should have access to the All Apps product license by adding them to the All Apps CC user group.
- Upload CSV file in Admin Console; validate all chosen users are now assigned to the All Apps CC user group.
Any users synced to the Adobe Admin Console via Google Sync after the user group initial setup must be manually placed into the user group, either one by one or using the bulk method described in step 6 above, to gain access to the All Apps CC license.
Verify that your Google Admin Console has API access enabled. To know more about how to enable API access, follow the instructions provided here.
Please check the User Provisioning status in the Google Admin Console. Users won't sync if User Provisioning is not activated.
To check this, sign in to the Google Admin Console. Then, from the Home page go to Apps > SAML apps > More controls > Adobe application > User provisioning. Activate provisioning (select ON for everyone) if it is turned off.
You can also refer to the G Suite Admin Help document Configure Adobe user provisioning for more details on setting up the Google Admin Console.
Existing Google users migration
The section covers some questions asked by admins who want to use Google Sync and are already using Google as their IdP.
To migrate existing non-Federated ID users to Federated ID type:
- Establish Google Sync with the chosen directory and domains.
- Sync users, including those who already have an existing non-Federated ID on the Console, via Google Sync. Any users with an existing non-Federated ID now have both a non-Federated ID and a Federated ID in the Admin Console.
- Use Edit Identity Type option in User tab to manually migrate chosen non-Federated ID users to their newly created Federated ID account; this triggers the automated asset migration for these users when they log in with their Federated ID for the first time.
Yes, when the user email is updated in the Google directory, the Adobe Admin Console email and username field gets updated accordingly.
To enable enterprise storage and other enterprise-level features, we're updating all existing Adobe IDs to Business IDs. All new business customers will use Business IDs for their team members.
You'll receive advance communication when your organization is scheduled for the update. For more information, see Introduction to Business IDs and new storage features. Until your organization is updated, you will continue to use Adobe ID type to access the organization. Support for Adobe IDs will then be reserved for individual customers only.