Navodila za uporabo Prekliči

Migrate to a new authentication provider

Išči

Zadnja posodobitev 23. avg. 2022

Adobe za podjetja in skupine: vodnik za skrbništvo
Načrtovanje uvedbe
Nastavitev organizacije
1. Vrste identitet | Pregled
2. Nastavitev identitete | Pregled
3. Nastavitev organizacije z Enterprise ID-jem
4. Nastavitev združevanja in sinhronizacije storitve Azure AD
5. Nastavitev združevanja in sinhronizacije Google
6. Nastavitev organizacije s storitvijo Microsoft ADFS
7. Nastavitev organizacije za okrožne portale in LMS
8. Nastavitev organizacije z drugimi ponudniki identitet
9. Pogosta vprašanja o enkratni prijavi in odpravljanju težav
Upravljanje nastavitve organizacije
Upravljanje uporabnikov
Upravljanje izdelkov in pravic
1. Upravljanje izdelkov in profilov izdelkov
2. Upravljanje licenc za naprave v skupni rabi
Predstavitev konzole Global Admin Console
Upravljanje prostora za shranjevanje in sredstev
1. Prostor za shranjevanje
2. Selitev sredstev
3. Povrnitev sredstev od uporabnika
4. Selitev sredstev študentov | Samo za izobraževanje
  1. Samodejna selitev sredstev študentov
  2. Selitev lastnih sredstev
Upravljanje storitev
1. Adobe Stock
2. Pisave po meri
3. Adobe Asset Link
4. Adobe Acrobat Sign
5. Creative Cloud za podjetja – brezplačno članstvo
  1. Pregled
Uvedba programov in posodobitev
1. Pregled
2. Ustvarjanje paketov
3. Prilagoditev paketov
  1. Prilagoditev namiznega programa Creative Cloud
  2. Vključitev razširitev v paket
4. Uvedba paketov
5. Upravljanje posodobitev
  1. Upravljanje sprememb za Adobejeve stranke podjetij in skupin
  2. Uvedba posodobitev
6. Nastavitveno orodje strežnika za posodabljanje Adobe (AUSST)
7. Adobe Remote Update Manager (RUM)
  1. Uporaba programa Adobe Remote Update Manager
  2. Odpravljanje napak v programu RUM
8. Odpravljanje težav
Upravljanje računa za skupine
Podaljšanje
1. Članstvo za skupine: podaljšanje
2. Podjetja v storitvi VIP: podaljšanje in skladnost
Upravljanje pogodb
Poročila in dnevniki
Pomoč

You can migrate your existing directory to a new authentication provider within the Adobe Admin Console. This allows you to choose an authentication provider based on your needs and seamlessly migrate your users along with their apps and assets.

Before you begin

To migrate to a new authentication provider, you must have the following:

Access to your organization's Adobe Admin Console with System Administrator credentials
An existing directory configured for federation in Admin Console
Access to your organization's identity provider portal (for example, Microsoft Azure Portal, Google Admin console, etc.)

You can find detailed information in Implementation Considerations.

Change your directory's identity provider

If you meet the access requirements and implementation considerations, follow the procedure below to edit your authentication profile and migrate your directory:

In your Adobe Admin Console, go to Settings > Directories > Edit the directory. Then, select Add new IdP in the directory Details.
Select the identity provider to set up the new authentication profile. Choose the identity provider (IdP) that your organization uses to authenticate users. Click Next.
Based on your choice of Identity provider, follow the steps below:
Log In to Azure with your Microsoft Azure Active Directory Global Admin credentials and Accept the permission prompt. You're taken back to the Directory details in the Admin Console.

Opomba:

The Microsoft Global Admin login is only required to create an application in the organization's Azure Portal. The Global Admin's login information is not stored, and only used for the one-time permission to create the application.

When selecting the identity provider for Step 3 above, the Microsoft Azure option should not be used if the Username field in the Adobe Admin Console does not match the UPN field in Azure Portal.
If the existing directory is configured to pass Username as the User Login Setting, the new IdP should be established under the Other SAML Providers' option. The login setting can be confirmed by selecting Edit option in the current directory under User Login Setting.

Choosing the Microsoft Azure' option in Step 3 only configures the identity provider and does not include directory sync services at this time.
Copy the ACS URL and Entity Id from the Edit SAML Configuration screen displays.

In a separate window, log in to the Google Admin Console with Google Admin credentials and navigate to Apps > SAML Apps.

Use the + sign to add new App and select Adobe app. Then, download the IDP metadata under Option 2 and upload it to the Edit SAML Configuration in the Adobe Admin Console. Then, click Save.

Confirm the Basic Information for Adobe. Enter the previously copied ACS URL and Entity ID in the Service Provider Details to finish. There is no need to set up User Provisioning as this is not currently supported for existing directories.

Last, go to Apps > SAML apps > Settings for Adobe > Service Status. Turn Service Status as ON for everyone and Save.
For Other SAML Providers:

Log in to your identity provider's application in a different window and create a new SAML app. (Do not edit the existing SAML app to prevent down-time for migration).

Based on your identity provider's settings, copy the Metadata file or ACS URL and Entity ID from the Adobe Admin Console to the identity provider's settings.

Upload metadata file from the identity provider setup to the Adobe Admin Console. Then, click Save.
In the Adobe Admin Console > Directory details, the new authentication profile is created. Use Test to verify whether the configuration functions correctly to ensure that all end users have access to SAML apps.

The Test feature ensures that the username format for the new authentication profile in their IdP matches the user information for the existing profile for user login.
Go to Directory users in the Adobe Admin Console > check that the identity provider usernames match Admin Console usernames.

For SAML, make sure that Subject field in the assertion from the new configuration matches the existing users' username format in the Admin Console.

Click Activate to migrate to the new authentication profile. Once done, the new profile displays In use.

After you've updated your directory setup, you can move domains from existing directories to the new directory using domain migration. Note that users of the migrated domains must be in the identity provider that is configured to work with the new target directory.

To know more about limitations and avoid errors that you might encounter while configuring, see Common questions.

Common questions: Directory migration

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. Also, consider the following points to ensure a seamless and error-free migration for your organization's directories:

Admins must create a new SAML app on their IdP setup to configure. If they edit the existing app, it will rewrite any active existing configuration, incur downtime, and nullify the ability to switch between available IdP’s in the Adobe Admin Console.
Admins must ensure that all required users are assigned to, or can use, the newly-created SAML app.
Admins must ensure the username format for the new authentication profile in their IdP matches what is used by the existing profile for user login. They can use the Test feature provided on the authentication profile to verify. This Test link can be copied to clipboard and share it with others to validate from their machines.
Admins should test the newly-added IdP before activation with 2 to 3 active accounts of the directory.

Error logs will not be available for these features. However, the Test workflow allows the Admin to validate relevant errors before activation. Limitations to consider include:

One directory can have up to two authentication profiles, and both the profiles should be for different authentication types. This means Microsoft Azure AD (which uses Open ID Connect) can stay with Other SAML providers, but Google (which itself uses SAML) cannot stay with Other SAML providers in the same directory.
This feature does not allow admins to migrate their identity provider to enable directory sync functionality (Azure AD Connector and Google Connector). Although customers migrating to Microsoft Azure or Google as their IdP can use a different form of user management strategy. To learn more, see Adobe Admin Console users.