The Adobe Admin Console offers a method for enterprise users to authenticate with Adobe enterprise offerings using their existing identity management systems via integration with Single Sign-On (SSO) enabled identity management systems. Single Sign-On is enabled using SAML, an industry-standard protocol which connects enterprise identity management systems to cloud service providers like Adobe. SSO can securely exchange authentication information between two parties: the service provider (Adobe) and your Identity Provider (IdP). The service provider sends a request to your IdP, which attempts to authenticate the user. After authentication, the IdP sends a response message to sign the user in. For detailed instructions, see Configure Single Sign-On.
Adobe offers the following identity types:
Yes, you can have a mix of Enterprise IDs, Federated IDs, and Adobe IDs, but not within the same claimed domain.
Enterprise ID and Federated ID are exclusive at the domain level. Therefore, you can choose only one of them. You can use Adobe ID in conjunction with either Federated ID or Enterprise ID.
For example, if an Enterprise claims only one domain, the IT Administrator can choose either Enterprise ID or Federated ID. If an organization claims multiple domains within an Enterprise, the IT Administrator can use one domain with Adobe IDs and Enterprise IDs, and another domain with Adobe IDs and Federated IDs, and so on. That means, for each domain, you can either have Enterprise ID or Federated ID along with Adobe ID.
Management of Adobe licenses under Federated ID is faster, easier, and more secure.
When signing in, your end users are redirected to your organization's standard – and familiar – Single Sign-On experience.
Yes, you can federate your enterprise directory and its login and authentication infrastructure with Adobe using your SAML 2.0 compliant identity provider.
No. When a domain is claimed for Federated IDs, nothing changes to existing Adobe IDs with email addresses in that domain. Existing Adobe IDs in the Admin Console are preserved.
Asset Migration is an automated process. When you initiate this process, all the supported content that is currently stored in your Adobe ID account is migrated to your Enterprise/Federated ID account. To learn more, see Automated Asset Migration.
Adobe’s Federated ID implementation supports authorization; authentication is handled by your Identity Provider (IdP).
As an enterprise organization, you can create a link between your authentication services (utilizing a corporate ID structure such as Active Directory) and Adobe's. This allows the enterprise organization to host the authentication. Adobe never stores passwords and IT administrators cannot reset passwords or edit user names for Federated IDs via the Adobe Admin Console.
No. Adobe interfaces with your identity provider and not directly to your enterprise directory. However, we support importing user and group information from your enterprise directory into the Adobe Admin Console. For more information, see Adding multiple users.
Adobe uses the secure and widely adopted industry standard Security Assertion Markup Language (SAML), which means the implementation of SSO integrates easily with any identity provider that supports SAML 2.0.
Following is a list of some IdPs that are SAML 2.0 compliant:
#If your identity provider is Microsft Azure AD or Google, you can skip the SAML-based method and use the Azure AD Connector or the Google Federation SSO to set up SSO with the Adobe Admin Console respectively. These setups are established and managed using the Adobe Admin Console and use a sync mechanism to manage user identities and entitlements.
Yes and the identity provider must be SAML 2.0 compatible.
At a minimum, your SAML identity provider must have:
Check with your identity provider if you have further questions.
No, breaking a 2048-bit certificate has never been done. And, the only people to have ever successfully cracked even a 768-bit certificate (the Lenstra group), estimated it would have taken them over 1000 years with the same hardware to crack even a 1024-bitcertificate (a feat roughly 32,000,000 times easier than cracking a 2048-bit certificate).
If you want to get the latest geeky data about estimates for cracking certificates of various lengths, go to this website. For a fun (accurate but marketing-oriented) picture of how secure these certificates are, go to this website (or its backing math website).
No, that limit is on the certificates used to encode the communication pipe between the browser and the server. Whereas these IdP certificates are used to sign (not encode) the data being passed through that encoded pipe. The browser never sees these certificates: they are only used between Adobe and the customer’s IdP.
You can get good, commercial-grade 2048-bit certificates for about $10/year of life. And, the certificates used by IdPs can be self-signed, which means they can be generated with open-source software for free.
No, because there are two other layers of strong encryption which check the IdP’s identity, that you'd have to crack before you could pose as the IdP. And, both of these other layers are not self-signed. Meaning, that you would have to crack not only the certificate that enforces the encryption but the certificate of the signer that generated that certificate.
For your premium support phone number and email address, see the Welcome email and PDF attachment that was sent to your account administrator.
The same URL endpoint may be used for multiple directories. However, the federation metadata will be managed separately for each IdP. So, the common IdP endpoint will need to handle requests whose content is different.
Yes, if the SAML integration of the directory uses username format and the user names on the Admin Console are identical to the persistent IDs provided. However, this would require that the persistent IDs must be available at the time users are sync’d into the Admin Console. This is not a common scenario and hence, in practice, persistent format for the NameID element would not be supported.
No. The NameID element value is used as the username on the Admin Console; the NameQualifier is ignored.
The first name, last name, and email assertion for each user are mandatory. However, they do not have to match the data in the directory, but the email must be unique for each user.
By default, Okta certificates are self-signed. By exception (and possibly for a fee) they can have the certificate signed by a public CA instead.
No. Sending notifications to end users via the Admin Console is not supported. As an enterprise customer, you need to distribute your own announcements after users are ready to begin with SSO with Adobe software and services.
No, If you remove or disable a user/ID from your enterprise directory, the user/ID is not removed or disabled from the Adobe Admin Console automatically. However, the user is no longer entitled and cannot sign in to the Adobe Creative Cloud desktop apps, services, mobile apps, or Acrobat DC apps. You need to manually remove the user/ID from the Admin Console.
Yes, you need to use the Adobe Admin Console to manage users, groups, and entitlements. Note, however, that once you create groups in the Admin Console, you can upload a CSV file including both user and group information. This creates the user account and places them in the designated group.
No, you cannot reset passwords for Federated IDs using the Adobe Admin Console. Adobe does not store user credentials. Use your Identity Provider for user management.
Find answers to your questions related to directory migration to a new authentication provider and updating a deprecated SAML setup.
Before you start, ensure you meet the access requirements to be able to follow the procedure for migrating to a different identity provider or updating a deprecated SAML setup. Also, consider the following points to ensure a seamless and error-free migration for your organization's directories:
Error logs will not be available for these features. However, the Test workflow allows the Admin to validate relevant errors prior to activation. Limitations to consider include: