Skip to main content

​
After this article

You will be able to connect Rapid7 to Lumos to sync users, groups, and roles from your Insight platform organization for visibility and Access Reviews.

​
Capabilities

​
Required plan and roles

  • Rapid7 role: a platform administrator must create the User API Key. User keys inherit the permissions of the account that creates them.
  • Permission scoping: this is a read-only integration. Lumos syncs users, groups, and roles but doesn’t provision or deprovision anything in Rapid7.
  • Activity tracking: supported. The connector syncs each user’s last login.

​
Read-only access vs provisioning

Is read-only possible? Yes, and it’s the only mode this connector supports. Rapid7 syncs users, groups, and roles for visibility, the connector doesn’t provision or deprovision anything in Rapid7. What read-only requires. A User API Key generated by a Rapid7 platform administrator. The key inherits the permissions of the account that created it, so follow the steps below to generate and connect it. Watch out for. Since the User API Key inherits the creating account’s permissions, generate it from an account whose privileges you’re comfortable extending to Lumos. There’s no separate provisioning mode or scope to request, this is a sync-only integration end to end.

​
Instructions

Phase 1: Generate a User API Key in Rapid7
  1. Log in to the Rapid7 Insight/Command Platform as a platform administrator.
  2. From the left menu of the Platform Home page, click Administration → API Key Management.
  3. On the User API Keys page, click Generate New User Key.
  4. Select the organization the key should apply to and give the key a name, then click Generate.
  5. Copy the key immediately. You can’t view it again after the window closes.
  6. Note your Storage Region. Lumos supports us, eu, ca, au, and ap. You can confirm your region from your Insight platform URL.
Phase 2: Connect in Lumos
  1. Find the Rapid7 card in your Lumos integrations (reconnect an existing card or add a new one).
  2. Enter the API Key, Organization ID, and Storage Region.
  3. Click Connect.

​
API Endpoints Used

​
Troubleshooting

Users aren’t appearing in Lumos. Verify the API key can read user data and hasn’t been revoked or expired. Make sure users have email addresses in their Rapid7 profiles and are active (not disabled). Review the Lumos integration logs for specific errors. “Invalid API key” or authentication failures. Confirm you copied the complete key without extra spaces. Check the key hasn’t been revoked in Rapid7. Verify the selected region matches where the key was issued. Generate a new User API Key if the original has issues. “Invalid region” or region-specific errors. Verify you selected the correct region (us, eu, ca, au, ap). Check your Insight platform URL to confirm the region. Make sure the API key is valid for that region. Contact Rapid7 support if you’re unsure which region your account uses.