Adobe License Management
On this page
Adobe License Management is an integration that runs as the Adobe License Management scheduled task. The task authenticates against the Adobe identity service and calls the Adobe User Management API. For how Alloy Navigator tracks software licenses in general, see Software Asset Management.
The Default Workflow supplies the integration as a scheduled task and six workflow parameters. This page describes what a new Alloy Navigator 2026.1 database created with the Default Workflow contains; see Default Workflow Configuration. When a database older than version 2025.1 is upgraded, the upgrade adds the Adobe License Management scheduled task, disabled, together with its six parameters; a parameter the database already has is left unchanged. An upgrade of a database from version 2025.1 or later does not add the task: such a database normally has it already, from its creation or an earlier upgrade, and a task that an administrator deleted is not restored. The parameter values this page gives as supplied are those of a new database, and in any database an administrator may have changed this content.
The task's own workflow steps reach Adobe at ims-na1.adobelogin.com and usermanagement.adobe.io. The integration is available on-premises and in Alloy Navigator Cloud.
Parameters
The task has six parameters: Organization ID, Client ID, Client Secret, Create Persons, Deallocate Licenses, and Safe Mode. The integration has no debug parameter.
Two of them have consequences for your data:
- Create Persons: when on, the task creates Person records for Adobe users it does not find in the database.
- Deallocate Licenses: when on, the task removes licenses from users who are absent from the Adobe response.
The settings page describes Safe Mode as "the job will run and produce a session log, but no data will be added or modified".
Create Persons, Deallocate Licenses, and Safe Mode are each set to on in the supplied configuration. With Safe Mode on, the first run after you enable the task is a dry run.
IMPORTANT: Read the Create Persons and Deallocate Licenses settings before a first run. In the supplied configuration both are on, and Safe Mode, also on, is what keeps the first run harmless. With Deallocate Licenses on, the task also removes allocations of an Adobe product's Software License that were made by hand, when their holder is not among the product's current Adobe users.
Third-party credentials such as these are stored as workflow parameter values, not with your accounts or mail profiles. In the supplied configuration, Client ID and Client Secret are encrypted parameters: the Settings App stores their values encrypted when you save them, and the product decrypts them for use. Treat an exported workflow file as sensitive: the encrypted values can be decrypted by the product.
Prepare Adobe
The task authenticates against Adobe with the credentials of a User Management API project in Adobe Developer Console. You need an Adobe enterprise account, and only a member of your Adobe organization with the System Admin role can create the integration for the User Management API. Adobe describes the role requirement in its User Management API authentication documentation.
- Sign in to Adobe Developer Console as a System Admin of your Adobe organization, and create a project.
- Add the User Management API to the project with an OAuth Server-to-Server credential. Adobe no longer creates Service Account (JWT) credentials; see Adobe's migration guide for Service Account (JWT) credentials.
- From the project's credential, copy the Client ID, the Client Secret, and the Organization ID. For where Adobe shows these values, see Adobe's OAuth Server-to-Server implementation guide.
- Enter the copied values in the Client ID, Client Secret, and Organization ID parameters, as described in Set the parameters.
Set the parameters
The parameters are on the integration's own settings page in Workflow Configuration, Integrations > Adobe License Management. In the Settings App, the Workflow Configuration node requires the administrative right that allows managing Workflow Configuration. In the Admin Center, the Workflow Configuration menu entry requires the Workflow Configuration permission; see Permissions Reference.
In the Settings App
- Under Workflow and Business Logic, open Workflow Configuration.
- In the category tree, select Integrations > Adobe License Management. The right pane shows one control per parameter, with its description.
- Enter the values and save your changes. Only the changed values of the selected category are saved.
In the Admin Center
- Under Workflow and Business Logic, open Workflow Configuration.
- Open Integrations > Adobe License Management. The page shows one control per parameter.
- Enter the values, and then click Save. Save and Cancel appear once you change a field. If you leave the page with unsaved changes, the Admin Center asks: "You should save you changes before leaving this page. Do you want to leave this page?"
The Admin Center's Workflow Configuration form does not check the values you enter against the parameter's type or declared validation rules.
How the task works
On the Adobe side, the task only reads. It obtains an access token from the Adobe identity service, and then reads the product profiles of your Adobe organization and the users assigned to each profile. It writes nothing to Adobe: when the task deallocates a license, it does so only in Alloy Navigator.
For each Adobe product, the task does the following in Alloy Navigator:
- Creates the manufacturer Adobe Systems if it does not exist yet.
- Finds or creates a Software Product for the Adobe product, with version 1.0.0.
- Finds or creates a Tracked Software record, and links the Software Product to it.
- Finds or creates a Software License with the Per Named User policy. For a Software License that already exists, the task overwrites its quantity with the total quota of the product's Adobe profiles.
- Allocates the license to the Person record of each Adobe user assigned to the product, unless the license is already allocated to that Person. The task does this on every run, whether Deallocate Licenses is on or off.
To find the Person record of an Adobe user, the task looks first for the Person it linked to that user in an earlier run, then for a Person with the user's e-mail address, and then among the Person records created in the same run. When it finds the Person in another way than through an earlier link, it records the link to the Adobe user for later runs. If more than one Person has the user's e-mail address, the task does not allocate the license.
The task does not change existing Person records. When no Person is found:
- With Create Persons on, the task creates a Person record with the name, full name, and primary e-mail address from Adobe, and logs the activity "Created via Adobe Integration" on it. The license is then allocated to the new Person.
- With Create Persons off, the task does not create the Person, and the license is not allocated to that user.
With Deallocate Licenses on, the task removes from the product's Software License every allocation whose holder is not among the product's current Adobe users, including allocations that were made by hand.
Enable and run the task
In the supplied configuration, the Adobe License Management scheduled task is disabled, so a new database makes no call to Adobe until an administrator supplies the credentials and enables the task.
The task is enabled, run, and its sessions read on the Scheduled Tasks pages of the Settings App and the Admin Center; see Scheduled Tasks.
Troubleshooting
Each run of the task writes a session log, which you read on the Scheduled Tasks pages. The integration has no debug parameter: the session log is what the task reports.
The session log shows the settings of the run: the entry "Adobe License Management 1.0", and the entries "Create Persons:", "Deallocate Licenses:", and "Safe Mode is on:", each with its value. With Safe Mode on, it also shows "SAFE MODE IS ON" and "CHANGES WILL NOT BE COMMITTED".
The other entries of the session log:
| Entry | What it tells you |
|---|---|
| "Processing Adobe Product: <product>" | The task has started on one Adobe product. |
| Entries that begin with "Found existing Software Product", "Found existing Tracked Software", or "Found existing Software License" | The record already existed and was used. |
| Entries that begin with "Created Software Product", "Created Tracked Software", or "Created Software License" | The task created the record. |
| "Processing Adobe user: <first name> <last name>", followed by the Adobe user name | The task has started on one Adobe user of the product. |
| Entries that begin with "Found existing Person record" or "Created a Person record" | The Person record the task found for the user, or created for the user. |
| "Found more than one Person with this email: <email>. License will not be allocated." | More than one Person record has the user's e-mail address, so the license is not allocated to the user. |
| "User not found in Navigator's database and will not be created due to job settings. The License will not be allocated." | No Person record was found for the user, and Create Persons is off. |
| "Allocated a license to the Person." | The task allocated the license to the Person. |
| "License is already allocated, nothing to do." | The Person already held an allocation of the license. |
| "Allocated: <N>", "Deallocated: <N>", and "Product Summary:" | The counts for one Adobe product. |
| "Total Created Software Products: <N>", "Total Created Tracked Software: <N>", "Total Created Software Licenses: <N>", and "Total Created Persons: <N>" | The totals of the run. |
| "Error occurred:", with the error message, its details, and the response from Adobe | A request to Adobe failed. |
The error text that comes with "Error occurred:" is not written by Alloy Navigator: it is the message of the failed request and the body of the response that Adobe returned.