Skip to main content

After this article

You will be able to connect New Relic to Lumos to sync users, groups, and roles.

Capabilities

Activity tracking is supported. Lumos tracks the last login timestamp for synced users so you can monitor access patterns.

Required plan and roles

  • New Relic role: no scopes are required for this integration, but the API key must be created by an Administrator.
  • New Relic plan: your plan must include User Management API access.

Read-only access vs provisioning

Is read-only possible? Yes, and it’s the only mode. This connector only syncs users, groups, and roles from New Relic. It doesn’t provision or deprovision anything there. What read-only requires. A New Relic User-type API key created by an Administrator, plus your Authentication Domain ID, on a plan with User Management API access. No specific scopes are required beyond that. Follow the steps below. Watch out for. The API key you generate carries whatever access the creating Administrator’s account has in New Relic. There’s no separate read-only key type, so key rotation or regeneration should go through an Administrator to avoid breaking the sync.

Instructions

Phase 1: Create an API key New Relic API keys authenticate requests and manage integrations with New Relic’s platform.
  1. Visit New Relic and log in to your account.
  2. Go to Account settings (click your profile icon).
  3. Select API Keys from the dropdown menu or the settings page.
  4. Click Create a key and create a User type key for the selected account.
  5. Copy and store the key right away, since it might not be shown again.
Phase 2: Find your Authentication Domain ID An Authentication Domain is a grouping of users governed by the same user management settings, such as how they’re provisioned and how they authenticate.
  1. Log in to your New Relic account.
  2. In the left-hand sidebar, click your account menu (your profile icon).
  3. Go to Administration → Authentication Domains.
  4. Copy the ID of the Authentication Domain you want to connect to this integration.
Phase 3: Connect in Lumos
  1. Click the New Relic card in your Lumos integrations (reconnect an existing card or add a new one).
  2. Provide the API Key and Authentication Domain ID.
  3. Click Connect.

API Endpoints Used

Troubleshooting

API key authentication failures (“Invalid API Key” or “Authentication failed”). Verify you copied the complete User key without extra spaces. Make sure the key hasn’t been deleted in New Relic. Check that the key type is User key, not License key or Browser key. Confirm your New Relic account is active and not suspended. Generate a new User key if the original may be compromised, and verify the key has access to the accounts you want to sync. Groups not appearing. Verify your User key has permission to view groups. Check that groups exist in your authentication domain and that each group has at least one member. Confirm you selected the correct authentication domain, then review New Relic’s user management settings. Users from multiple authentication domains not syncing correctly. Verify your User key has access to all authentication domains. Check that every domain is configured properly in New Relic. If you use SAML or SCIM, make sure SSO domains are set up, then review domain-specific group memberships. Contact New Relic support if domain access issues persist. GraphQL query errors. Verify NerdGraph API access is enabled for your account, and check New Relic’s API status page for service issues. Make sure your User key has the required query permissions. If you see “Too many requests,” review rate limiting. Disconnecting and reconnecting the integration can also clear the error.