Set up a Delinea connector

C1 provides identity governance for Delinea. Integrate your Delinea instance with C1 for unified visibility and governance over user access.

This connector is in beta. This means it’s undergoing ongoing testing and development while we gather feedback, validate functionality, and improve stability. Beta connectors are generally stable, but they may have limited feature support, incomplete error handling, or occasional issues.

We recommend closely monitoring workflows that use this connector and contacting our Support team with any issues or feedback.

Capabilities

Resource	Sync	Provision
Account
Group
Role
Team

Additional functionality:

None.

Gather Delinea configuration information

Configuring the connector requires you to pass in information from Delinea. Gather these configuration details before you move on.

Here’s the information you’ll need:

• Secret Server Base URL — your Secret Server base URL, i.e. the server root only. For Secret Server Cloud this looks like https://<your-tenant>.secretservercloud.com.
• Delinea Platform URL — your Delinea Platform tenant URL (e.g. https://<your-tenant>.delinea.app). This is used only to sign the connector in, and is different from the Secret Server base URL.
• Client ID — the username/client ID of a Delinea Platform service user.
• Client Secret — that service user’s password/client secret.

The connector signs in to the Delinea Platform as a service user to read data from Secret Server. Create one in the Delinea Platform, then use its username as the Client ID and its password as the Client Secret.

To create the service user:

1. In the Delinea Platform, go to Access > Users, open the More dropdown, and select Add service user.
2. Complete the required fields and select Next. The username and password you set here are the connector’s Client ID and Client Secret.
3. A new service user has no permissions, so add it to a group or role that grants only the access it needs to read users (and, if you’re syncing them, groups, roles, and teams).

When the service user is created, a matching application account is automatically created in Secret Server, so no extra setup is needed there.

For more detail, see the Delinea documentation on adding users and using Secret Server APIs from the Delinea Platform.

Configure the Delinea connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in C1
• Access to the set of Delinea configuration information gathered by following the instructions above

Cloud-hosted

Follow these instructions to use a built-in, no-code connector hosted by C1.

1. In C1, navigate to Integrations > Connectors and click Add connector.

2. Search for Delinea and click Add.

3. Choose how to set up the new Delinea 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
4. 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.

5. Click Next.

6. Find the Settings area of the page and click Edit.

7. Enter the configuration information from the previous section.

8. Click Save.

9. The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

Done. Your Delinea connector is now pulling access data into C1.

Self-hosted

Follow these instructions to use the Delinea 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

Contact C1’s support team to download the latest version of the connector.

Step 1: Set up a new Delinea connector

1. In C1, navigate to Integrations > Connectors > Add connector.

2. Search for Baton and click Add.

3. Choose how to set up the new Delinea 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
4. 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.

5. Click Next.

6. In the Settings area of the page, click Edit.

7. 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 Delinea connector deployment:

Secrets configuration

# baton-delinea-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-delinea-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>

  # Delinea config
  BATON_SECRET_SERVER_BASE_URL: <Secret Server root URL, e.g. https://your-tenant.secretservercloud.com>
  BATON_DELINEA_PLATFORM_URL: <Delinea Platform URL, e.g. https://your-tenant.delinea.app>
  BATON_DELINEA_CLIENT_ID: <Delinea Platform service user client ID>
  BATON_DELINEA_CLIENT_SECRET: <Delinea Platform service user client secret>

See the connector’s README or run --help to see all available configuration flags and environment variables.

Deployment configuration

# baton-delinea.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-delinea
  labels:
    app: baton-delinea
spec:
  selector:
    matchLabels:
      app: baton-delinea
  template:
    metadata:
      labels:
        app: baton-delinea
        baton: true
        baton-app: delinea
    spec:
      containers:
      - name: baton-delinea
        image: public.ecr.aws/conductorone/baton-delinea:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-delinea
        envFrom:
        - secretRef:
            name: baton-delinea-secrets

Step 3: Deploy the connector

1. Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.

2. 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 Delinea connector to. Delinea data should be found on the Entitlements and Accounts tabs.

Done. Your Delinea connector is now pulling access data into C1.