Keeper

Overview

The Keeper integration connects one node of your Keeper enterprise to Oneleet through Keeper’s SCIM API, syncing the node’s users as user account assets and vendor accounts. This lets Oneleet track who has a Keeper account.

What does Oneleet monitor?

• Keeper users in the connected node and its sub-nodes, including their email, name, and whether the account is active

Keeper’s SCIM API doesn’t expose two-factor authentication status or administrator roles, so Oneleet doesn’t report them for Keeper accounts.

Setup

To set up the Keeper integration, navigate to Integrations > Add integration > Keeper.

Oneleet connects with a SCIM provisioning token and the node ID it belongs to. You must be a Keeper Administrator to create one.

1. In the Keeper Admin Console, go to Admin and select the node that contains your users. Keeper doesn’t allow SCIM on the top-level root node, so pick (or create with ⋮ → Add Node) a node underneath it.
2. Open the Provisioning tab and click Add Method.
3. Select SCIM (System for Cross-Domain Identity Management) and click Next.
4. Copy the number at the end of the URL (https://keepersecurity.com/api/rest/scim/v2/<node>) into the Node field in Oneleet.
5. Click Generate, copy the token into the API Key field in Oneleet, and click Next in Keeper to save the method.
6. Click Connect in Oneleet.

Keeper allows only one SCIM method per branch of the node tree, so you can’t add one to a node whose parent or sub-node already has SCIM. If a SCIM method already exists on the node you want, open it and click Reset Provisioning Token to get a new token. Resetting the token disconnects anything that used the old one, including Oneleet, until you update it.

Oneleet only sees users in the selected node and its sub-nodes. Users placed directly in the root node aren’t returned by Keeper’s SCIM API.