Set up a New Relic connector

Capabilities

Resource	Sync	Provision
Organizations
Roles
Groups
Users

The New Relic connector supports account provisioning: creating and deleting users, and adding or removing users from groups.

Connector actions

Connector actions are custom capabilities that extend C1 automations with app-specific operations. You can use connector actions in the Perform connector action automation step.

Action name	Additional fields	Description
update_user	`user_id` (resource reference, required), `name` (string, optional), `email` (string, optional), `user_type` (string, optional: `BASIC_USER_TIER`, `CORE_USER_TIER`, or `FULL_USER_TIER`)	Updates a New Relic user’s full name, email address, and/or user tier. At least one of `name`, `email`, or `user_type` must be provided; any field left blank is unchanged. Returns `success` (boolean) and `user_id` (the ID of the updated user).

Find your authentication domain ID

New Relic organizes users into authentication domains, and every new user must be created within one. C1 needs this domain’s ID before it can create New Relic accounts.

From the New Relic user menu, go to Administration > Authentication domains.

Select the authentication domain you want new users created in.

Copy the domain ID shown at the top of the authentication domain page. You’ll use it in the next section.

See New Relic’s authentication domains documentation for more detail.

Set up account provisioning mappings

C1 creates a New Relic account when a user requests access to this app. The account details come from the app’s provisioning mappings, which you set up on the app’s Overview page — see Configure account provisioning for the full procedure. The New Relic connector requires four mappings:

Destination value	Source value
`name`	A CEL expression resolving to the user’s full name, such as `subject.display_name`
`email`	A CEL expression resolving to the user’s email address, such as `subject.email`
`user_type`	The New Relic tier new accounts receive, as a quoted string: `"BASIC_USER_TIER"`, `"CORE_USER_TIER"`, or `"FULL_USER_TIER"`
`authentication_domain_id`	The domain ID you copied above, as a quoted string

Enter user_type and authentication_domain_id as quoted CEL string literals — "BASIC_USER_TIER", not BASIC_USER_TIER. These two are fixed values rather than expressions, so every account this app creates lands in the same tier and the same authentication domain. Set up a separate app for each tier or domain you need to provision into.

Gather New Relic credentials

Configuring the connector requires you to pass in credentials generated in New Relic. Gather these credentials before you move on.

A user who is a full platform user in New Relic must perform this task.To use account provisioning (create/delete users or add users to groups), the API key owner must also have the Authentication domain manager role in New Relic. See New Relic user management for details.

Create a user API key

Log into New Relic as a full platform user.

At the bottom of the left navigation bar, click your username and select API Keys.

Click Create a key. The Create an API key drawer opens.

Select User as the Key type.

Enter a name for the new API key, such as “C1”, and add any notes you or your colleagues might need about this key.

Click Create a key.

The new key is generated and added to the list of API keys.

Click the … menu and select Copy key. Carefully save the API key.

That’s it! Next, move on to the connector configuration instructions.

Configure the New Relic connector

To complete this task, you’ll need:

The Connector Administrator or Super Administrator role in C1
Access to the set of New Relic credentials generated by following the instructions above

Cloud-hosted
Self-hosted

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

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

Search for New Relic and click Add.

Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.

Set the connector’s Name and, optionally, a Description.

Click the pencil icon next to Owners to choose who can configure and manage this connector.

Click Add. The connector is created and its configuration page opens.

Find the Settings area of the page and click Edit.

Paste the user API key into the API key field.

Click Save.

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

That’s it! Your New Relic connector is now pulling access data into C1.

Follow these instructions to use the New Relic 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 New Relic connector

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

Search for Baton and click Add.

Set the connector’s Name and, optionally, a Description.

Click the pencil icon next to Owners to choose who can configure and manage this connector.

Click Add. The connector is created and its configuration page opens.

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 New Relic connector deployment:

Secrets configuration

# baton-newrelic-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-newrelic-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>
  
  # New Relic credentials
  BATON_APIKEY: <New Relic API key>

  # 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

# baton-newrelic.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-newrelic
  labels:
    app: baton-newrelic
spec:
  selector:
    matchLabels:
      app: baton-newrelic
  template:
    metadata:
      labels:
        app: baton-newrelic
        baton: true
        baton-app: newrelic
    spec:
      containers:
      - name: baton-newrelic
        image: public.ecr.aws/conductorone/baton-newrelic:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-newrelic
        envFrom:
        - secretRef:
            name: baton-newrelic-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 New Relic connector to. New Relic data should be found on the Entitlements and Accounts tabs.

That’s it! Your New Relic connector is now pulling access data into C1.

Welcome

Manage connectors

Deploy connectors

Upload connector data

Configurable connectors

Pre-built connectors

Set up a New Relic connector

Capabilities

Connector actions

Find your authentication domain ID

Set up account provisioning mappings

Gather New Relic credentials

Create a user API key

Configure the New Relic connector

Resources

Step 1: Set up a new New Relic connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector

​Capabilities

​Connector actions

​Find your authentication domain ID

​Set up account provisioning mappings

​Gather New Relic credentials

​Create a user API key

​Configure the New Relic connector

​Resources

​Step 1: Set up a new New Relic connector

​Step 2: Create Kubernetes configuration files

​Secrets configuration

​Deployment configuration

​Step 3: Deploy the connector

Capabilities

Connector actions

Find your authentication domain ID

Set up account provisioning mappings

Gather New Relic credentials

Create a user API key

Configure the New Relic connector

Resources

Step 1: Set up a new New Relic connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector