Kasutusjuhend Tühista

Resolve Federated ID (SSO) sign-in errors

Otsi
Enterprise

Enterprise

Admin Console
  1. Adobe ettevõtetele ja meeskondadele: administreerimisjuhend
  2. Juurutamise planeerimine
    1. Põhimõisted
      1. Litsentsimine
      2. Identiteet
      3. Kasutajate haldamine
      4. Rakenduste juurutamine
      5. Admin Console'i ülevaade
      6. Administraatori rollid
    2. Juurutamisjuhised
      1. Nimeliste kasutajate juurutamisjuhend
      2. SDL juurutamisjuhend
      3. Adobe Acrobati juurutamine 
    3. Creative Cloud haridusasutustele – juurutamine
      1. Kasutuselevõtt kodus
      2. K-12 sisseelamisviisard
      3. Lihtne seadistus
      4. Kasutajate sünkroniseerimine
      5. Roster Sync K-12 (USA)
      6. Peamised litsentsimispõhimõtted
      7. Kasutuselevõtmise valikud
      8. Kiireid näpunäiteid
      9. Adobe rakenduste kinnitamine Google Admin Console'is
      10. Adobe Expressi lubamine Google Classroomis
      11. Integratsioon Canvas LMS-iga
      12. Integratsioon Blackboard Learniga
      13. SSO konfigureerimine piirkonna portaalide ja LMS-ide jaoks
      14. Kasutajate lisamine nimekirja sünkroonimise kaudu
      15. Kivuto KKK
      16. Esmaste ja teiseste asutuste õiguste suunised
  3. Oma organisatsiooni seadistamine
    1. Identiteeditüübid | Ülevaade
    2. Identiteedi seadistamine | Ülevaade
    3. Organisatsiooni seadistamine Enterprise ID-ga
    4. Azure AD föderatsiooni ja sünkroonimise seadistamine
      1. SSO seadistamine Microsoftiga Azure OIDC kaudu
      2. Azure'i sünkroonimise lisamine oma kataloogi
      3. Hariduse rollide sünkroonimine
      4. Azure Connectori KKK
    5. Google'i föderatsiooni ja sünkroonimise seadistamine
      1. SSO seadistamine Google'i föderatsiooniga
      2. Google Synci lisamine teie kataloogile
      3. Google'i föderatsiooni KKK
    6. Organisatsiooni seadistamine Microsoft ADFS-iga
    7. Organisatsiooni seadistamine piirkonna portaalide ja LMS-i jaoks
    8. Organisatsiooni seadistamine koos teiste identiteedi pakkujatega
      1. Kataloogi loomine
      2. Domeeni omandiõiguse kontrollimine
      3. Domeenide lisamine kataloogidele
    9. SSO levinud küsimused ja tõrkeotsing
      1. SSO levinud küsimused
      2. SSO tõrkeotsing
      3. Hariduse levinud küsimused
  4. Teie organisatsiooni seadistamise haldamine
    1. Olemasolevate domeenide ja kataloogide haldamine
    2. Automaatse konto loomise lubamine
    3. Organisatsiooni seadistamine kataloogi usalduse kaudu
    4. Üleminek uuele autentimise pakkujale 
    5. Varade sätted
    6. Autentimise sätted
    7. Privaatsuse ja turvalisuse kontaktid
    8. Konsooli sätted
    9. Krüpteerimise haldamine  
  5. Kasutajate haldamine
    1. Ülevaade
    2. Administratiivsed rollid
    3. Kasutajate haldamise strateegiad
      1. Kasutajate individuaalne haldamine   
      2. Mitme kasutaja haldamine (hulgi CSV)
      3. Kasutajate sünkroonimisvahend (UST)
      4. Microsoft Azure'iga sünkroonimine
      5. Google'i föderatsiooniga sünkroonimine
    4. Litsentside määramine Teamsi kasutajale
    5. Rakendusesisene kasutajate haldamine meeskondade jaoks
      1. Meeskonna haldamine Adobe Expressis
      2. Meeskonna haldamine Adobe Acrobatis
    6. Ühtivate e-posti domeenidega kasutajate lisamine
    7. Kasutaja identiteedi tüübi muutmine
    8. Kasutajarühmade haldamine
    9. Kataloogi kasutajate haldamine
    10. Arendajate haldamine
    11. Olemasolevate kasutajate migreerimine Adobe Admin Console'i
    12. Kasutajate haldamise migreerimine Adobe Admin Console'i
  6. Toodete ja õiguste haldamine
    1. Toodete ja tooteprofiilide haldamine
      1. Toodete haldamine
      2. Toodete ja litsentside ostmine
      3. Ettevõtte kasutajate tooteprofiilide haldamine
      4. Automaatse määramise reeglite haldamine
      5. Kasutajatele Firefly kohandatud mudelite treenimise õiguse andmine
      6. Tootetaotluste läbivaatamine
      7. Iseteeninduse poliitikate haldamine
      8. Rakenduste integratsioonide haldamine
      9. Toodete õiguste haldamine Admin Console'is  
      10. Teenuste lubamine/keelamine tooteprofiili jaoks
      11. Üks rakendus | Creative Cloud ettevõtetele
      12. Valikulised teenused
    2. Jagatud seadmete litsentside haldamine
      1. Mis on uut
      2. Juurutamisjuhend
      3. Pakettide loomine
      4. Litsentside taastamine
      5. Profiilide haldamine
      6. Litsentsimise tööriistakomplekt
      7. Jagatud seadmete litsentsimise KKK
  7. Global Admin Console'iga alustamine
    1. Globaalse administreerimise kohandamine
    2. Organisatsiooni valimine
    3. Organisatsiooni hierarhia haldamine
    4. Tooteprofiilide haldamine
    5. Administraatorite haldamine
    6. Kasutajarühmade haldamine
    7. Organisatsiooni poliitikate uuendamine
    8. Poliitikamallide haldamine
    9. Lasteorganisatsioonidele toodete eraldamine
    10. Ootel tööde käivitamine
    11. Ülevaadetega tutvumine
    12. Organisatsiooni struktuuri eksportimine või importimine
  8. Salvestusruumi ja varade haldamine
    1. Salvestusruum
      1. Ettevõtte salvestusruumi haldamine
      2. Adobe Creative Cloud: salvestusruumi uuendamine
      3. Adobe salvestusruumi haldamine
    2. Varade migratsioon
      1. Automatiseeritud varade migratsioon
      2. Automatiseeritud varade migratsiooni KKK  
      3. Ülekantud varade haldamine
    3. Varade tagasinõudmine kasutajalt
    4. Üliõpilaste varade migratsioon | ainult EDU
      1. Automaatne üliõpilaste varade migratsioon
      2. Teie varade migratsioon
  9. Teenuste haldamine
    1. Adobe Stock
      1. Adobe Stocki krediidipaketid meeskondadele
      2. Adobe Stock ettevõtetele
      3. Adobe Stock ettevõtetele kasutamine
      4. Adobe Stocki litsentside heakskiitmine
    2. Kohandatud fondid
    3. Adobe Asset Link
      1. Ülevaade
      2. Kasutajarühma loomine
      3. Adobe Experience Manageri varade konfigureerimine
      4. Adobe Asset Linki konfigureerimine ja installimine
      5. Varade haldamine
      6. Adobe Asset Link XD jaoks
    4. Adobe Acrobat Sign
      1. Adobe Acrobat Signi seadistamine ettevõtte või meeskondade jaoks
      2. Adobe Acrobat Sign – meeskonna funktsiooni administraator
      3. Adobe Acrobat Signi haldamine Admin Console'is
    5. Creative Cloud ettevõtetele – tasuta liikmesus
      1. Ülevaade
  10. Rakenduste ja uuenduste juurutamine
    1. Ülevaade
      1. Rakenduste ja uuenduste juurutamine ja tarnimine
      2. Juurutamise planeerimine
      3. Juurutamise ettevalmistus
    2. Pakettide loomine
      1. Rakenduste pakendamine Admin Console'i kaudu
      2. Nimeliste kasutajate litsentsipakettide loomine
      3. Eelgenereeritud pakettide haldamine
        1. Adobe mallide haldamine
        2. Üksikrakenduse pakettide haldamine
      4. Pakettide haldamine
      5. Seadmete litsentside haldamine
      6. Seerianumbrite litsentsimine
    3. Pakettide kohandamine
      1. Creative Cloudi töölauarakenduse kohandamine
      2. Laienduste kaasamine teie paketti
    4. Pakettide juurutamine 
      1. Pakettide juurutamine
      2. Adobe pakettide juurutamine Microsoft Intune'i abil
      3. Adobe pakettide juurutamine SCCM-iga
      4. Adobe pakettide juurutamine ARD-ga
      5. Toodete installimine erandite kausta
      6. Creative Cloudi toodete desinstallimine
      7. Adobe provisioning toolkit enterprise editioni kasutamine
    5. Uuenduste haldamine
      1. Adobe ettevõtte ja meeskondade klientide muutuste haldamine
      2. Uuenduste juurutamine
    6. Adobe Update Server Setup Tool (AUSST)
      1. AUSST ülevaade
      2. Sisemise uuenduste serveri seadistamine
      3. Sisemise uuenduste serveri haldamine
      4. AUSST tavalised kasutusjuhud   
      5. Sisemise värskenduste serveri tõrkeotsing
    7. Adobe Remote Update Manager (RUM)
      1. Väljalaskemärkmed
      2. Adobe Remote Update Manageri kasutamine
    8. Tõrkeotsing
      1. Creative Cloudi rakenduste installimise ja deinstalleerimise vigade tõrkeotsing
      2. Klientide masinate päring, et kontrollida, kas pakett on kasutusele võetud
  11. Meeskonnakonto haldamine
    1. Ülevaade
    2. Makseandmete uuendamine
    3. Arvete haldamine
    4. Lepinguomaniku muutmine
    5. Plaani vahetamine
    6. Edasimüüja muutmine
    7. Plaanist loobumine
    8. Ostutaotluse nõuetele vastavus
  12. Uuendamised
    1. Meeskonnaplaanide liikmesus: uuendamine
    2. Ettevõtte VIP: uuendamised ja nõuetele vastavus
  13. Lepingute haldamine
    1. ETLA lepingute automatiseeritud aegumise etapid
    2. Lepingutüüpide vahetamine olemasolevas Adobe Admin Console'is
    3. Value Incentive Plan (VIP) Hiinas
    4. VIP Select abi
  14. Aruanded ja logid
    1. Auditilogi
    2. Määramise aruanded
    3. Sisulogid
  15. Abi saamine
    1. Ühenduse võtmine Adobe klienditeenindusega
    2. Meeskonnakontode tugivõimalused
    3. Ettevõtluskontode tugivõimalused
    4. Experience Cloudi tugivõimalused

Resolve common authentication errors, verify configurations, and troubleshoot login problems related to Federated ID (SSO) in Adobe products. Get tips to fix SAML errors, certificate issues, and other authentication challenges.

Märkus.

Refer to the following articles if your organization has set up SSO via Google Federation or Microsoft Azure Sync:

Overview

After successfully configuring SSO within the Adobe Admin Console, ensure that you select Download Adobe Metadata file and save 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.

Download Adobe Metadata file

Basic troubleshooting

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, a Creative Cloud application, or Adobe.com)

Solutions to other common errors

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" while signing 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 with the right product, or the product isn't 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.
  • Your SSO client uses JavaScript as part of the login process, and you're attempting to log in to a client that doesn't support JavaScript.

How to resolve:

  • Check the username and email in the Adobe Admin Console and match the value with the NameID and Email attribute in the SAML logs.
  • 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 don't match the email address that was used to start the login process.

Run a SAML trace 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:

  1. Open the AD FS Management application on your server, and within the folder AD FS > Service > Endpoints, select the Federation Metadata.

  2. 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.

    Märkus.

    Accept any warnings if prompted.

  3. On the Settings tab of the Admin Console and navigate to Identity Settings > 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:

w32tm /resync

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

Märkus.

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" or "The status of the SAML request was not successful" or "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:

Laadi alla

Hankige fail
SAML Working Example

With Microsoft ADFS:

  1. 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.
  2. Access the dashboard. 
  3. Click the Identity tab and the domain.
  4. Click Edit Configuration.
  5. Locate IDP Binding. Switch to HTTP-POST and then save. 
  6. Retest the login experience.
  7. If it works but you prefer the prior setting, simply switch back to HTTP-REDIRECT and reupload the metadata into ADFS.

With other IdPs:

  1. Encountering error 400 means that a successful login was rejected by your IdP.
  2. Check your IdP logs for the source of the error.
  3. Correct the issue and try again.

Error: "403 malfunctioned certificate"

Update the certificate in Google Console under the Adobe SAML app and re-upload the metadata files in the Adobe Admin Console.

Error: "403 app_not_configured_for_user"

Update Entity ID in the Google Console. Then export the metadata file and upload it in the Adobe Admin Console.

Error: "you cannot access this right now" or "you can't get there from here"

This error generally occurs when the organization has enabled the Conditional Access Policy in IdP.

If you are using managed packages to deploy products, create a managed package from the Adobe Admin Console by selecting the browser-based authentication option. Then, deploy it on the user's device.

If not, the users can open the Creative Cloud Desktop application, and select Sign in using your browser from the Help menu.

Error: "App Not Assigned"

In this case, the admin must add the users to the Adobe SAML app created on their IdP. Learn to create an Adobe SAML app on Google Admin console or Microsoft Azure Portal.

Error: "You do not have access to this service. Contact your IT administrator to gain access or sign in with an Adobe ID"

Check the SAML logs, as the username or email address being sent in the SAML assertion does not match the information entered in the Admin Console.

Saage abi kiiremini ja hõlpsamalt

Uus kasutaja?

Kiirlingid

Vaadake kõiki oma plaane Plaanide haldamine
Vaadake kiirlinke
Peitke kiirlingid

Legal Notices    |    Online Privacy Policy