> ## Documentation Index
> Fetch the complete documentation index at: https://www.c1.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# 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:
* Base URL
* Token
See the Delinea docs for information on how to acquire credentials: [View the documentation](https://updates.thycotic.net/secretserver/restapiguide/11.6.3/OAuth#tag/Authentication/operation/OAuth2Service_Authorize)
## 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
**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 **Delinea** and click **Add**.
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
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**.
Enter the configuration information from the previous section.
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 Delinea connector is now pulling access data into C1.
**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](mailto:support@c1.ai) to download the latest version of the connector.
### Step 1: Set up a new Delinea connector
In C1, navigate to **Integrations** > **Connectors** > **Add connector**.
Search for **Baton** and click **Add**.
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
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 Delinea connector deployment:
#### Secrets configuration
```yaml theme={"theme":{"light":"css-variables","dark":"css-variables"}}
# baton-delinea-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
name: baton-delinea-secrets
type: Opaque
stringData:
# C1 credentials
BATON_CLIENT_ID:
BATON_CLIENT_SECRET:
# Delinea config
BATON_DELINEA_BASE_URL:
BATON_DELINEA_TOKEN:
```
See the connector's README or run `--help` to see all available configuration flags and environment variables.
#### Deployment configuration
```yaml expandable theme={"theme":{"light":"css-variables","dark":"css-variables"}}
# 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: ghcr.io/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
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 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.