Capabilities

Available hosting methods

Choose the hosting method that best suits your needs:

Gather New Relic credentials

Each setup method 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.

Create a user API key

1. Log into New Relic as a full platform user.

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

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

4. Select User as the Key type.

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

6. Click Create a key.

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

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

That’s it! Next, move on to the instructions for your chosen setup method.

Set up a New Relic cloud-hosted connector

To complete this task, you’ll need:

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

1. In ConductorOne, navigate to Admin > Connectors and click Add connector.

2. Search for New Relic and click Add.

3. Choose how to set up the new New Relic 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 ConductorOne)

   • 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 ConductorOne users. Setting multiple owners is allowed.

   If you choose someone else, ConductorOne 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. Paste the user API key into the API key field.

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.

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

Set up a New Relic cloud-hosted connector using Terraform

As an alternative to the cloud-hosted setup process described above, you can use Terraform to configure the integration between New Relic and ConductorOne.

See the ConductorOne New Relic integration resource page in the ConductorOne Terraform registry for example usage and the full list of required and optional parameters.

Set up a New Relic self-hosted connector

To complete this task, you’ll need:

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

When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with ConductorOne, automatically syncing and uploading data at regular intervals. This data is immediately available in the ConductorOne UI for access reviews and access requests.

Why use Kubernetes? Kubernetes provides automated deployment, scaling, and management of your connectors. It ensures high availability and reliable operation of your connector services.

Step 1: Configure the New Relic connector

1. In ConductorOne, navigate to Connectors > Add connector.

2. Search for Baton and click Add.

3. Choose how to set up the new New Relic 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 ConductorOne)

   • 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 ConductorOne users. Setting multiple owners is allowed.

   If you choose someone else, ConductorOne 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 New Relic connector deployment:

Secrets configuration

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

  # Optional: include if you want ConductorOne 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: ghcr.io/conductorone/baton-newrelic:latest
        imagePullPolicy: IfNotPresent
        envFrom:
        - secretRef:
            name: baton-newrelic-secrets

Step 3: Deploy the connector

1. Create a namespace in which to run ConductorOne connectors (if desired):

   kubectl create namespace conductorone
   

2. Apply the secret configuration:

   kubectl -n conductorone apply -f baton-newrelic-secrets.yaml
   

3. Apply the deployment:

   kubectl -n conductorone apply -f baton-newrelic.yaml
   

Step 4: Verify the deployment

1. Check that the deployment is running:

   kubectl -n conductorone get pods
   

2. View the connector logs:

   kubectl -n conductorone logs -l app=baton-${baton-newrelic}
   

3. Check that the connector data uploaded correctly. In ConductorOne, click Applications. 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 ConductorOne.