Panduan Pengguna Batal

Resolve Federated ID (SSO) sign-in errors

Cari
Enterprise

Enterprise

Admin Console
  1. Adobe Enterprise & Teams: Panduan pentadbiran
  2. Rancang pemasangan anda
    1. Konsep asas
      1. Pelesenan
      2. Identiti
      3. Pengurusan pengguna
      4. Pemasangan aplikasi
      5. Gambaran keseluruhan Admin Console
      6. Peranan pentadbir
    2. Panduan Pemasangan
      1. Panduan pemasangan Pengguna Bernama
      2. Panduan pemasangan SDL
      3. Pasangkan Adobe Acrobat 
    3. Pasangkan Creative Cloud untuk pendidikan
      1. Laman utama Penerapan
      2. Bestari Penyesuaian Tugas K-12
      3. Persediaan mudah
      4. Menyegerakkan Pengguna
      5. Penyegerakan Senarai K-12 (AS)
      6. Konsep pelesenan utama
      7. Pilihan penerapan
      8. Petua cepat
      9. Luluskan aplikasi Adobe dalam Google Admin Console
      10. Dayakan Adobe Express dalam Google Classroom
      11. Penyepaduan dengan Canvas LMS
      12. Penyepaduan dengan Blackboard Learn
      13. Mengkonfigurasikan SSO untuk District Portal dan LMS
      14. Tambahkan pengguna melalui Roster Sync
      15. Soalan Lazim Kivuto
      16. Garis panduan kelayakan institusi Utama dan Sekunder
  3. Sediakan organisasi anda
    1. Jenis identiti | Gambaran keseluruhan
    2. Sediakan identiti | Gambaran keseluruhan
    3. Sediakan organisasi dengan Enterprise ID
    4. Sediakan Azure AD federation dan segerakkan
      1. Sediakan SSO dengan Microsoft melalui Azure OIDC
      2. Tambahkan Azure Sync pada direktori anda
      3. Penyegerakan peranan untuk Pendidikan
      4. Soalan Lazim Azure Connector
    5. Sediakan Google Federation dan segerakkan
      1. Sediakan SSO dengan Google Federation
      2. Tambahkan Google Sync pada direktori anda
      3. Soalan Lazim Google federation
    6. Sediakan organisasi dengan Microsoft ADFS
    7. Sediakan organisasi untuk District Portal dan LMS
    8. Sediakan organisasi dengan penyedia Identiti lain
      1. Cipta direktori
      2. Sahkan pemilikan domain
      3. Tambahkan domain pada direktori
    9. Soalan lazim dan penyelesaian masalah SSO
      1. Soalan lazim SSO
      2. Penyelesaian masalah SSO
      3. Soalan lazim pendidikan
  4. Urus persediaan organisasi anda
    1. Urus domain dan direktori sedia ada
    2. Dayakan penciptaan akaun automatik
    3. Sediakan organisasi melalui amanah direktori
    4. Berhijrah kepada penyedia pengesahan baharu 
    5. Tetapan aset
    6. Tetapan pengesahan
    7. Hubungan privasi dan keselamatan
    8. Tetapan konsol
    9. Urus penyulitan  
  5. Urus pengguna
    1. Gambaran Keseluruhan
    2. Peranan pentadbiran
    3. Strategi pengurusan pengguna
      1. Urus pengguna secara individu   
      2. Urus berbilang pengguna (CSV Pukal)
      3. Alat Penyegerakan Pengguna (UST)
      4. Microsoft Azure Sync
      5. Google Federation Sync
    4. Berikan lesen kepada pengguna Pasukan
    5. Pengurusan pengguna dalam apl untuk pasukan
      1. Urus pasukan anda dalam Adobe Express
      2. Urus pasukan anda dalam Adobe Acrobat
    6. Tambahkan pengguna dengan domain e-mel yang sepadan
    7. Tukar jenis identiti pengguna
    8. Urus kumpulan pengguna
    9. Urus pengguna direktori
    10. Urus pembangun
    11. Hijrahkan pengguna sedia ada ke Adobe Admin Console
    12. Hijrahkan pengurusan pengguna ke Adobe Admin Console
  6. Urus produk dan kelayakan
    1. Urus produk dan profil produk
      1. Urus produk
      2. Beli produk dan lesen
      3. Urus profil produk untuk pengguna perusahaan
      4. Urus peraturan pemberian automatik
      5. Beri hak kepada pengguna untuk melatih model tersuai Firefly
      6. Semak permintaan produk
      7. Urus dasar layan diri
      8. Urus penyepaduan aplikasi
      9. Urus kebenaran produk dalam Admin Console  
      10. Dayakan/lumpuhkan perkhidmatan untuk profil produk
      11. Aplikasi Tunggal | Creative Cloud untuk perusahaan
      12. Perkhidmatan pilihan
    2. Urus lesen Peranti yang Dikongsi
      1. Apa yang baharu
      2. Panduan pemasangan
      3. Cipta pakej
      4. Pulihkan lesen
      5. Urus profil
      6. Kit alat pelesenan
      7. Soalan Lazim Pelesenan Peranti yang Dikongsi
  7. Bermula dengan Global Admin Console
    1. Amalkan pentadbiran global
    2. Pilih organisasi anda
    3. Urus hierarki organisasi
    4. Urus profil produk
    5. Urus pentadbir
    6. Urus kumpulan pengguna
    7. Kemas kini dasar organisasi
    8. Urus templat dasar
    9. Peruntukkan produk kepada organisasi anak
    10. Laksanakan kerja yang belum selesai
    11. Terokai insights
    12. Eksport atau import struktur organisasi
  8. Urus storan dan aset
    1. Storan
      1. Urus storan perusahaan
      2. Adobe Creative Cloud: Kemas kini kepada storan
      3. Urus storan Adobe
    2. Penghijrahan Aset
      1. Penghijrahan Aset Automatik
      2. Soalan Lazim Penghijrahan Aset Automatik  
      3. Urus aset yang dipindahkan
    3. Tuntut semula aset daripada pengguna
    4. Penghijrahan aset pelajar | EDU sahaja
      1. Penghijrahan aset pelajar automatik
      2. Hijrahkan aset anda
  9. Urus perkhidmatan
    1. Adobe Stock
      1. Pek kredit Adobe Stock untuk pasukan
      2. Adobe Stock untuk perusahaan
      3. Guna Adobe Stock untuk perusahaan
      4. Kelulusan Lesen Adobe Stock
    2. Fon tersuai
    3. Pautan Aset Adobe
      1. Gambaran Keseluruhan
      2. Cipta kumpulan pengguna
      3. Konfigurasikan Adobe Experience Manager Assets
      4. Konfigurasikan dan pasang Adobe Asset Link
      5. Urus aset
      6. Adobe Asset Link untuk XD
    4. Adobe Acrobat Sign
      1. Sediakan Adobe Acrobat Sign untuk perusahaan atau pasukan
      2. Adobe Acrobat Sign - Pentadbir ciri Pasukan
      3. Urus Adobe Acrobat Sign pada Admin Console
    5. Creative Cloud untuk perusahaan - keahlian percuma
      1. Gambaran Keseluruhan
  10. Pasangkan aplikasi dan kemas kini
    1. Gambaran Keseluruhan
      1. Pasangkan dan hantar aplikasi dan kemas kini
      2. Pelan untuk dipasangkan
      3. Bersedia untuk dipasangkan
    2. Cipta pakej
      1. Pakej aplikasi melalui Admin Console
      2. Cipta Pakej Pelesenan Pengguna Bernama
      3. Urus pakej yang dijana terlebih dahulu
        1. Urus templat Adobe
        2. Urus pakej aplikasi Tunggal
      4. Urus pakej
      5. Urus lesen peranti
      6. Pelesenan nombor siri
    3. Sesuaikan pakej
      1. Sesuaikan app desktop Creative Cloud
      2. Sertakan sambungan dalam pakej anda
    4. Pasangkan Pakej 
      1. Pasangkan pakej
      2. Pasangkan pakej Adobe menggunakan Microsoft Intune
      3. Pasangkan pakej Adobe dengan SCCM
      4. Pasangkan pakej Adobe dengan ARD
      5. Pasang produk dalam folder Pengecualian
      6. Nyahpasang produk Creative Cloud
      7. Gunakan kit alat peruntukan Adobe edisi perusahaan
    5. Urus kemas kini
      1. Tukar pengurusan untuk pelanggan Adobe enterprise and teams
      2. Pasangkan kemas kini
    6. Adobe Update Server Setup Tool (AUSST)
      1. Gambaran Keseluruhan AUSST
      2. Sediakan pelayan kemas kini dalaman
      3. Mengekalkan pelayan kemas kini dalaman
      4. Kes penggunaan biasa AUSST   
      5. Selesaikan masalah pelayan kemas kini dalaman
    7. Adobe Remote Update Manager (RUM)
      1. Nota keluaran
      2. Gunakan Adobe Remote Update Manager
    8. Selesaikan masalah
      1. Selesaikan masalah ralat pemasangan dan penyahpasangan aplikasi Creative Cloud
      2. Tanya mesin klien untuk menyemak sama ada pakej dipasangkan
  11. Urus akaun Pasukan anda
    1. Gambaran Keseluruhan
    2. Kemas kini butiran bayaran
    3. Uruskan invois
    4. Tukar pemilik kontrak
    5. Tukar pelan anda
    6. Tukar penjual semula
    7. Batalkan pelan anda
    8. Pematuhan Permintaan Pembelian
  12. Pembaharuan
    1. Keahlian pasukan: Pembaharuan
    2. Perusahaan dalam VIP: Pembaharuan dan pematuhan
  13. Urus kontrak
    1. Tahap tamat tempoh automatik untuk kontrak ETLA
    2. Menukar jenis kontrak dalam Adobe Admin Console sedia ada
    3. Value Incentive Plan (VIP) di China
    4. Bantuan VIP Select
  14. Laporan & log
    1. Log Audit
    2. Laporan pemberian
    3. Log Kandungan
  15. Dapatkan bantuan
    1. Hubungi Layanan Pelanggan Adobe
    2. Pilihan sokongan untuk akaun pasukan
    3. Pilihan sokongan untuk akaun perusahaan
    4. Pilihan sokongan untuk Experience Cloud

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.

Nota:

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.

    Nota:

    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

Nota:

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:

Muat turun

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

Dapatkan bantuan dengan lebih pantas dan mudah

Pengguna baharu?

Pautan pantas

Lihat semua pelan anda Urus pelan anda
Lihat pautan pantas
Sembunyikan pautan pantas

Legal Notices    |    Online Privacy Policy