Príručka používateľa Zrušiť

Set up identity and Single Sign-On

Vyhľadať

Posledná aktualizácia dňa 11. 5. 2023 | Vzťahuje sa tiež na Creative Cloud for enterprise, Document Cloud for enterprise

Enterprise

Admin Console

Adobe Enterprise & Teams: Príručka pre administráciu
Plánovanie nasadenia
1. Základné pojmy
2. Príručky nasadenia
3. Nasadenie programu Creative Cloud na vzdelávacie účely
Nastavenie organizácie
1. Typy identity | Prehľad
2. Nastavenie identity | Prehľad
3. Nastavenie organizácie pomocou Enterprise ID
4. Nastavenie federácie a synchronizácie Azure AD
5. Nastavenie služby Google Federation a synchronizácia
6. Nastavenie služby Microsoft ADFS pre organizáciu
7. Nastavenie organizácie pre okresné portály a LMS
8. Nastavenie organizácie pre iných poskytovateľov identity
9. Časté otázky o jednotnom prihlásení a riešenie problémov
Správa nastavenia organizácie
Správa používateľov
Správa produktov a nárokov
1. Správa produktov a profilov produktov
2. Správa zdieľaných licencií zariadení
Začíname s konzolou Global Admin Console
Správa úložiska zdrojov
1. Úložisko
2. Migrácia zdrojov
3. Opätovné získanie zdrojov od používateľa
4. Migrácia študentských zdrojov | Iba oblasť vzdelávania
  1. Automatická migrácia študentských zdrojov
  2. Migrácia vašich zdrojov
Správa služieb
1. Adobe Stock
2. Vlastné písma
3. Adobe Asset Link
4. Adobe Acrobat Sign
5. Creative Cloud pre podniky – bezplatné členstvo
  1. Prehľad
Nasadenie aplikácií a aktualizácií
1. Prehľad
2. Vytvorenie balíkov
3. Prispôsobenie balíčkov
  1. Prispôsobenie počítačovej aplikácie Creative Cloud
  2. Zahrnutie rozšírení do balíka
4. Nasadenie balíkov
5. Správa aktualizácií
  1. Správa zmien pre podnikových a tímových zákazníkov Adobe
  2. Nasadenie aktualizácií
6. Nástroj na nastavenie servera Adobe Update (AUSST)
7. Adobe Remote Update Manager (RUM)
  1. Použitie nástroja Adobe Remote Update Manager
  2. Riešenie chýb nástroja RUM
8. Riešenie problémov
Správa tímových kont
Obnovenie
1. Členstvo v službe Teams: obnovenia
2. Spoločnosť s plánom VIP: Obnovenie licencií a dodržiavanie zmluvných podmienok
Správa zmlúv
Prehľady a protokoly
Získať pomoc

Learn how to set up your users' accounts with different ID types with or without Single Sign-on. Set up SSO for Adobe software, configure SAML settings, and go through the most common questions and errors.

Set up identity and SSO | YouTube video

Key terms and concepts

A directory in the Admin Console is an entity that holds resources such as users and policies like authentication. These directories are similar to LDAP or Active Directories.

Organization identity provider such as Active Directory, Microsoft Azure, Ping, Okta, InCommon, or Shibboleth.

System admin Works with IdP directory managers and DNS managers to set up identity in the Admin Console.

DNS Manager Updates DNS tokens to validate domain ownership

Identity Provider (IdP) directory manager Handles the IdP portal and associated connectors

Created, owned, and managed by the end user. Adobe performs the authentication, and the end user manages the identity. Depending upon the storage model, users or businesses retain control over files and data.

For organizations that have been updated to the Enterprise storage model, assets and data is controlled by the organization. For organizations that have not been updated, the individual owns and controls Adobe ID assets.

Created, owned, and managed by an organization. Adobe hosts the Enterprise ID and performs authentication, but the organization maintains the Enterprise ID. Admins create an Enterprise ID and issue it to a user. Admins can revoke access to products and services by taking over the account or deleting the Enterprise ID to permanently block access to associated data. Learn more

Created and owned by an organization, and linked to the enterprise directory via federation. The organization manages credentials and processes Single Sign-On via a SAML2 Identity Provider (IdP).

The following are a few requirements and scenarios where Federated IDs are recommended:

If you want to provision users based on your organization's enterprise directory.
If you want to manage the authentication of users.
If you need to maintain strict control over apps and services available to a user.

Set up identity without Single Sign-On

You may use Adobe ID or Enterprise ID if your organization is currently not using SSO on other applications.

Using Adobe ID

We're updating all organizations to the Enterprise storage model. This gives your organization greater control over your users' assets and data.

Get started with adding users to your Admin Console.

Set up identity with Enterprise ID

You can set up an Enterprise ID directory if you want more control on your users' data without using SSO. Only Admins create an Enterprise ID and issue it to a user.

See Set up organization with Enterprise ID to know the requirements and steps involved in creating Enterprise ID directories.

Set up identity with Single Sign-On

You must set up your user identity with Federated ID accounts to use SSO. The following are a few requirements and scenarios where Federated IDs are recommended:

If you want to provision users based on your organization's enterprise directory.
If you want to manage the authentication of users.
If you need to maintain strict control over apps and services available to a user.

Set up a new SSO integration

You can use popular identity providers such as Microsoft Azure AD, Google, or use other SAML-based IdP to set up SSO between your organization and Adobe products.

Azure AD (Recommended)

Set up SSO and user-sync with Azure AD Connector

Other SAML IdP

Set up SSO with other SAML-providers

Integrate with any standard SAML-compliant Identity Provider (IdP).

Google (Recommended)

Set up SSO and user-sync using Google Connector

Manage existing SSO setup

Follow the next steps after you have set up an SSO between your organization and Adobe:

Learn how to manage your domains and directories:

Manage users and groups
Link domains to directories to decide users' access to apps, services, and settings
Manage directory trust to use domains claimed by another organization