Open the AD FS Management application on your server, and within the folder AD FS > Service > Endpoints, select the Federation Metadata.
Unable to sign in to Adobe products, services, or mobile apps with Federated ID (SSO): Troubleshooting errors
- 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
This article does not apply to SSO setups using Google federation or Microsoft Azure Sync.
Refer to the following articles if your organization has set up SSO via any of these identity providers:
After successfully configuring SSO within the Adobe Admin Console, ensure that you clicked Download Adobe Metadata file and have saved the SAML XML Metadata file to your computer. Your identity provider requires this file to enable single sign-on. Import the XML configuration details properly into your identity provider (IdP). This is required for SAML integration with your IdP and will make sure that the data is configured properly.
If you have questions as to how to use the SAML XML Metadata file to configure your IdP, reach out to your IdP directly for instructions, which vary per IdP.
Issues with single sign-on are often caused by basic errors that are easy to overlook. In particular, check the following:
- The user is assigned to a product profile with an entitlement.
- The user name sent to SAML matches the user name in the enterprise dashboard.
- Check all entries in Admin Console and your identity provider for spelling or syntax errors.
- The Creative Cloud desktop app has been updated to the latest version.
- The user is logging in to the correct place (Creative Cloud desktop app, Creative Cloud application, or Adobe.com)
Error "An error occurred" with button labeled "Try Again"
This error typically occurs after user authentication has succeeded and Okta has successfully forwarded the authentication response to Adobe.
In the Adobe Admin Console, validate the following:
On the Identity tab:
- Ensure that the associated domain has been activated.
On the Products tab:
- Ensure that the user is associated to the correct product nickname and in the domain you claimed to be configured as Federated ID.
- Ensure that the product nickname has the correct entitlements assigned to it.
On the Users tab:
- Ensure that the user name of the user is in the form of a complete email address.
Error "Access Denied" logging in
Possible causes for this error:
- The user name or email address being sent in the SAML assertion does not match the information entered in the Admin Console.
- The user isn't associated to the right product, or the product is not associated with the correct entitlement.
- The SAML user name is coming across as something other than an email address. All users must be in the domain you claimed as part of the setup process.
How to resolve:
- Verify the dashboard configuration for the user: user information and product profile.
- Run a SAML trace and validate that the information being sent matches the dashboard, and then correct any inconsistencies.
Error "Another user is currently logged in"
The error "another user is currently logged in" occurs when the attributes sent in the SAML assertion do not match the email address that was used to start the login process.
Check and ensure that the user's email address to log in matches the following:
- User's email address listed in the Admin Console
- User's username passed back in the NameID field of the SAML Assertion
Error "The Issuer in the SAML response did not match the issuer configured for the identity provider"
IDP Issuer in the SAML Assertion is different from what has been configured in the Inbound SAML. Look for typos (such as http vs https). When checking the IDP Issuer string with the customer SAML system, you're looking for an EXACT match to the string they provided. This issue comes up sometimes because a slash was missing at the end.
If you need assistance with this error, provide a SAML trace and values you entered in the Adobe dashboard.
Error "The digital signature in the SAML response did not validate with the identity provider's certificate"
This issue occurs when your directory's certificate has expired. To update the certificate, you must download the certificate or metadata from Identity provider and upload it in the Adobe Admin Console.
For example, follow the steps below if your IdP is Microsoft AD FS:
Use a browser to navigate to the URL provided against Federation Metadata and download the file. For example, https://<your AD FS hostname>/FederationMetadata/2007-06/FederationMetadata.xml.Opomba:
Accept any warnings if prompted.
Sign in to your Adobe Admin Console and navigate to Settings > Identity > Directories. Select the directory to update and click Configure on the SAML provider card.
Then, upload the IdP metadata file and Save.
Error "The current time is before the time-range specified in the assertion conditions"
Windows-based IdP Server:
1. Ensure that the system clock is synchronized with an accurate time server.
Check the accuracy system clock against your time server with this command; the "Phase Offset" value should be a small fraction of a second:
w32tm /query /status /verbose
You can cause an immediate resynchronization the system clock with the Time Server with the following command:
If the system clock is set correctly and you are still seeing the above error, you may must adjust the time-skew setting to increase the tolerance of the difference between clocks between the server and client.
2. Increase the allowed difference in system clock between servers.
From a Powershell window with administrative rights, set the allowed skew value to 2 minutes. Check whether you are able to log in, and then either increase or decrease the value depending on the result.
Determine the current time-skew setting for the relevant Relying Party Trust with the following command:
Get-ADFSRelyingPartyTrust | Format-List -property Identifier,Name,NotBeforeSkew
The Relying Party Trust is identified by the URL shown in the "Identifier" field of the output of the previous command for that particular configuration. This URL is also shown in the ADFS Management utility in the properties window for the relevant Relying Party Trust on the "Identifiers" tab in the field "Relying Party Trusts", as shown in the screenshot below.
Set the time skew to 2 minutes with the following command, substituting the Identifier address accordingly:
Set-ADFSRelyingPartyTrust –TargetIdentifier 'https://www.okta.com/saml2/service-provider/xxxxxxxxxxxxxxxxxxxx' –NotBeforeSkew 2
UNIX-based IdP Server
Ensure that the system clock is set correctly either using the ntpd service, or manually with the ntpdate command from a root shell or with sudo as shown below (note that if the time is offset by more than 0.5 seconds, the change will not happen immediately, but it will slowly correct the system clock). Ensure that the timezone is also set correctly.
# ntpdate -u pool.ntp.org
This works with identity providers such as Shibboleth.
Error 401 unauthorized credentials
This error occurs when the application does not support Federated login and must be logged into as an Adobe ID. FrameMaker, RoboHelp, and Adobe Captivate are examples of applications with this requirement.
Error "Inbound SAML login failed with message: The SAML response contained no assertions"
Check the login workflow. If you're able to access the sign-in page on another machine or network but not internally, the problem could be a block agent string. Also, run a SAML trace and confirm that First Name, Last Name, and Username as a properly formatted email address are in the SAML subject.
Error 400 bad request / Error "The status of the SAML request was not successful" / SAML certification validation failed
Validate that the proper SAML assertion is being sent:
- Not having a NameID element in the subject. Validate that the Subject element contains a NameId element. It must be equal to the Email attribute, which should be the email address of the user that you want to authenticate.
- Spelling errors, especially easily overlooked ones like https vs http.
- Validate that the correct certificate was provided. IDPs must be configured to use uncompressed SAML request/responses.
A utility such as SAML Tracer for Firefox can help unpack the assertion and display it for inspection. If you need assistance from Adobe Customer Care, you will be asked for this file. For details, see how to perform a SAML trace.
The following working example may help in properly formatting your SAML assertion:
With Microsoft ADFS:
- Every Active Directory account must have an email address listed in Active Directory to successfully log in (event log: The SAML response does not have NameId in the assertion). Check this first.
- Access the dashboard.
- Click the Identity tab and the domain.
- Click Edit Configuration.
- Locate IDP Binding. Switch to HTTP-POST and then save.
- Retest the login experience.
- If it works but you prefer the prior setting, simply switch back to HTTP-REDIRECT and reupload the metadata into ADFS.
With other IdPs:
- Encountering error 400 means that a successful login was rejected by your IdP.
- Check your IdP logs for the source of the error.
- Correct the issue and try again.