> ## Documentation Index
> Fetch the complete documentation index at: https://conductorone-jorge-mcp-resources-documentation.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.
# Set up Adobe connector
> C1 provides identity governance and just-in-time provisioning for Adobe. Integrate your Adobe instance with C1 to run user access reviews (UARs) and enable just-in-time access requests.
## Availability
This connector requires Adobe enterprise-level licenses. Standard Creative Cloud or individual Adobe product licenses are not supported.
## Capabilities
| Resource | Sync | Provision |
| :--------------- | :------------------------------------------------------------ | :------------------------------------------------------------ |
| Accounts | | |
| Groups | | |
| Product profiles | | |
**Additional functionality:**
The Adobe connector supports [automatic account provisioning and deprovisioning](/product/admin/account-provisioning).
Product profiles are synced with license seat data — purchased seats (from the profile's license quota) and consumed seats (from its member count) — so you can track license utilization per product.
## Limitations
* **Product profiles cannot be created through the connector.** Adobe's User Management API does not support creating product profiles; create them in the Adobe Admin Console. The connector syncs existing product profiles and provisions membership only.
* **Email addresses are case-sensitive.** Adobe's User Management API treats user email addresses as case-sensitive. Provisioning actions must use the exact casing Adobe has on file, or they will not match the intended user.
## Account provisioning
The Adobe connector supports creating new user accounts directly from C1. When configuring an account provisioning policy, you can map the following fields.
### Required fields
| Field | Description |
| :------ | :--------------------------------------------------------------- |
| `email` | The user's email address. Used as the login identifier in Adobe. |
### Optional fields
| Field | Description | Default |
| :-------------- | :--------------------------------------------------------------------------------------------------------------------------------------------- | :------------ |
| `identity_type` | The type of Adobe identity to create. Must be one of `federatedID`, `enterpriseID`, or `adobeID`. See [Identity types](#identity-types) below. | `federatedID` |
| `first_name` | The user's first name. Required when `identity_type` is `federatedID` or `enterpriseID`. | None |
| `last_name` | The user's last name. Required when `identity_type` is `federatedID` or `enterpriseID`. | None |
| `country` | Two-letter ISO 3166-1 country code (for example, `US`). Required when `identity_type` is `federatedID`. | None |
### Identity types
Adobe's User Management API supports three identity types. Choose the one that matches how your organization manages the user's email domain.
| Value | Description |
| :------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `federatedID` | For users whose email domain is owned and federated by your Adobe organization (SAML/SSO). `first_name`, `last_name`, and `country` are required. Use this for employees whose identity is managed through your identity provider. |
| `enterpriseID` | For users managed directly by your Adobe organization without federated SSO. `first_name` and `last_name` are required; `country` is optional. |
| `adobeID` | For users with a personal Adobe ID, typically external collaborators whose email domain is not claimed by any Adobe organization. All fields are optional. |
**`adobeID` cannot be used for email domains owned by another Adobe organization.** If the user's email domain is claimed by another organization's federated or enterprise directory, Adobe will reject the request with an error. In that case, the user must be provisioned by the organization that owns the domain, or use `federatedID` / `enterpriseID` if your organization owns the domain.
## Gather Adobe credentials
Configuring the connector requires you to pass in credentials generated in Adobe. Gather these credentials before you move on.
**Important**
A user with the **System Administrator** or **Product Administrator** role in Adobe Admin Console must perform this task.
### Look up your organization ID
In the Adobe Admin console, navigate to **Settings** > **Organization**.
Make a note of your organization ID (it's in `ABC123@AdobeOrg` format).
### Create a new OAuth Server-to-Server credential
In the Adobe Admin console, create a new project.
Click **Add API** and select **User Management API**.
* To give C1 sync-only (READ) access, give the User Management API **read access**
* To give C1 sync and provision (READ/WRITE) access, give the User Management API **read/write access** and **Product Profile management permissions**
Choose the **OAuth Server-to-Server** authentication type.
Click **Save configured API**.
Locate the **Credentials** section of the project and carefully copy and save the client ID and client secret.
**Done.** Next, move on to the connector configuration instructions.
## Configure the Adobe connector
**To complete this task, you'll need:**
* The **Connector Administrator** or **Super Administrator** role in C1
* Access to the set of Adobe credentials generated by following the instructions above
**Follow these instructions to use a built-in, no-code connector hosted by C1.**
In C1, navigate to **Integrations** > **Connectors** and click **Add connector**.
Search for **Adobe** and click **Add**.
Choose how to set up the new Adobe connector:
* Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren't yet managed with C1)
* Add the connector to a managed app (select from the list of existing managed apps)
* Create a new managed app
Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of C1 users. Setting multiple owners is allowed.
If you choose someone else, C1 will notify the new connector owner by email that their help is needed to complete the setup process.
Click **Next**.
Find the **Settings** area of the page and click **Edit**.
Paste the client ID, client secret, and organization ID into the relevant fields.
Click **Save**.
The connector's label changes to **Syncing**, followed by **Connected**. You can view the logs to ensure that information is syncing.
**Done.** Your Adobe connector is now pulling access data into C1.
**Follow these instructions to use the Adobe connector, hosted and run in your own environment.**
When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1 UI for access reviews and access requests.
### Resources
* [Official download center](https://dist.conductorone.com/ConductorOne/baton-adobe): For stable binaries (Windows/Linux/macOS) and container images.
### Step 1: Set up a new Adobe connector
In C1, navigate to **Integrations** > **Connectors** > **Add connector**.
Search for **Baton** and click **Add**.
Choose how to set up the new Adobe connector:
* Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren't yet managed with C1)
* Add the connector to a managed app (select from the list of existing managed apps)
* Create a new managed app
Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of C1 users. Setting multiple owners is allowed.
If you choose someone else, C1 will notify the new connector owner by email that their help is needed to complete the setup process.
Click **Next**.
In the **Settings** area of the page, click **Edit**.
Click **Rotate** to generate a new Client ID and Secret.
Carefully copy and save these credentials. We'll use them in Step 2.
### Step 2: Create Kubernetes configuration files
Create two Kubernetes manifest files for your Adobe connector deployment:
#### Secrets configuration
```yaml expandable theme={null}
# baton-adobe-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
name: baton-adobe-secrets
type: Opaque
stringData:
# C1 credentials
BATON_CLIENT_ID:
BATON_CLIENT_SECRET:
# Adobe credentials
BATON_ADOBE_CLIENT_ID:
BATON_ADOBE_CLIENT_SECRET:
BATON_ADOBE_ORGANIZATION_ID:
# Optional: include if you want C1 to provision access using this connector
BATON_PROVISIONING: "true"
```
See the connector's README or run `--help` to see all available configuration flags and environment variables.
#### Deployment configuration
```yaml expandable theme={null}
# baton-adobe.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
name: baton-adobe
labels:
app: baton-adobe
spec:
selector:
matchLabels:
app: baton-adobe
template:
metadata:
labels:
app: baton-adobe
baton: "true"
baton-app: adobe
spec:
containers:
- name: baton-adobe
image: public.ecr.aws/conductorone/baton-adobe:latest
imagePullPolicy: IfNotPresent
env:
- name: BATON_HOST_ID
value: baton-adobe
envFrom:
- secretRef:
name: baton-adobe-secrets
```
### Step 3: Deploy the connector
Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.
Check that the connector data uploaded correctly. In C1, click **Apps**. On the **Managed apps** tab, locate and click the name of the application you added the Adobe connector to. Adobe data should be found on the **Entitlements** and **Accounts** tabs.
**Done.** Your Adobe connector is now pulling access data into C1.