Manage device authentication for Creative Cloud and Acrobat Pro

Last updated on Jun 4, 2025

Applies to:

  • Persona: System Administrator
  • OS: macOS and Windows
  • Device: Company-owned desktop machines
  • Surface: Latest Version of Creative Cloud and Acrobat Pro desktop applications

Currently does not support:

  • Web services (such as Adobe Acrobat Sign, Adobe Assets, Adobe Libraries)
  • Mobile Applications
  • Acrobat Reader
  • Dreamweaver

Overview

This setting lets you configure how Creative Cloud desktop apps and Acrobat Pro desktop authenticate users, combined with your device deployment process. When users sign in, they're automatically redirected to your identity provider (IdP) for the domain you've claimed.

Note

To use this feature, claim your domain in Adobe Admin Console. You can claim multiple domains, but each device must resolve to a single claimed domain. If you've claimed multiple domains, you can redirect different users to different domains.

Benefits

Configuring authentication settings for your organization lets you:

  • Automatically redirect users to your identity provider at app launch, for domains claimed in Admin Console
  • Restrict sign-in to Organizational IDs only
  • Remove social sign-in options from the authentication screen

Configure device authentication

macOS

Create a plist file that specifies the claimed domain to redirect users to.

Place the plist file at:

/Library/Preferences/com.adobe.NGL.AuthInfo.plist

Restart the device to apply the change.

Windows

Open Windows Registry Editor.
Press Windows + R, type regedit and press Enter.

Navigate to the following location:

Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Adobe\

Add a key – NGL.

Within NGL, add another key – AuthInfo.

Within AuthInfo, create a string value:
Name: login_domain
Value: The name the claimed domain to which the user is redirected.

Windows registry value

Restart the device to apply the change.

Common questions

No. This configuration does not impact trust relationships.

No. Users must authenticate with a Federated ID account.

No. Wildcards are not allowed when specifying a domain. You must specify an exact domain, without wildcards.

This configuration will not work if browser-based login is configured by the admin.