Skip to main content

Overview

Lexful is an integration for Password Rotation, similar ITGlue and Hudu. Connecting it to MSP Process allows Password Rotation write each newly rotated password straight into the matching Lexful record, so your documentation always holds the current credentials. Setup is quick: generate an API key in Lexful, add it to MSP Process as a Security Integration, and map your clients to their Lexful organizations. Lexful only comes into play once Password Rotation is setup, as it is a place where rotated passwords get stored.

Prerequisites

  1. Password Rotation set up for the customers you’ll store credentials for — the DC agent (on-prem) or the M365 Identity Management app (cloud-only) deployed. Lexful is only relevant once rotation is running.
  2. A Lexful account with access to the Platform → APIs Keys area to generate an API key.
  3. Access to Settings → Integrations → Security Integrations in MSP Process.
  4. The Lexful organization that each MSP Process client maps to.

How to Setup

Step 1 — Generate an API key in Lexful.

  1. Sign in as an Admin in Lexful and navigate to Platform → APIs Keys.
  1. Click + New Key to create an API key for MSP Process.
  2. Note: The Account ID that will be used for the MSP Process security integration will be located on this page.
  1. Enter a name and click Create Key.
  1. A Your API key is ready will appear displaying the Key ID and a Secret.
  2. Copy these values and paste them into the Lexful security integration in MSP Process.
  3. Note: Copy the Secret now!
  4. It’s shown only once, on this page. As soon as you navigate away it can’t be retrieved again. If you lose it, you will need to generate a new key.

Step 2 — Add Lexful in MSP Process.

  1. Go to Settings → Integrations → Security Integrations and click + (Add).
  1. Choose Lexful.
  1. Enter a Name, the Account ID, the Key ID (API key), and Secret from Step 1.
  1. Note: For partners in regions outside of the US, please contact Lexful Support to confirm the API URL.
  2. Click Submit.

Step 3 — Map your clients to Lexful organizations.

  1. Once connected, MSP Process pulls in your customers.
  2. For each customer, map the MSP Process client to its matching Lexful organization.
  3. This tells us where to write rotated credentials and where to look for an existing record.
  1. Once you click the Plus sign in the Actions Column, a dropdown will appear under Organization.
  2. This is where you can select the correct company mapping
That’s the whole setup. Rotated passwords for mapped clients can now be stored in Lexful.

Mapping Warning

If you run into the warning that the company has been mapped, but the vault is not enabled for the client after selecting the organization, please follow the steps below to resolve.
  1. Navigating to Identity Management → Password Management → Rotation → Clients
  1. Locate the company you need to enable the mapping for, then click the Manage Security Integration from the Actions column.
  1. Select the Vault you’d like to enable
  1. Click Save

Add a new client to Lexful later

  1. First, create the client’s organization in Lexful if it doesn’t already exist. The mapping needs an organization to point to.
  1. In MSP Process, go to Settings → Integrations → Security Integrations → Lexful and map the client: match the MSP Process client to its Lexful organization.
  2. Select Lexful as the storage target on the rotation policy that covers them (Rotations → Policies).
  3. New rotations for that client then flow to Lexful automatically, no need to touch the API key or reconnect the integration.

Good to know

  1. The Secret appears only once. Paste it into MSP Process (Step 2) before leaving the Lexful key page.
  2. To replace it later, you will need to generate a new key in Lexful and update the integration.
  3. If you already use ITGlue or Hudu, the flow is nearly identical.
  4. The only real difference is where you get the API key. Everything on the MSP Process side (add integration, map clients) works the same way.
  5. You control storage per policy.
  6. For sensitive, admin-level credentials, most MSPs push to Lexful.
  7. For ordinary user credentials you’d rather not be responsible for storing, you can leave them out of Lexful. That choice is made on each rotation policy, not here.

Limitations

Mapping is required.

  1. A client with no Lexful organization mapped has nowhere for its credentials to land. You will need to map every client you intend to store in Lexful.

Nothing stores in Lexful on its own.

  1. Credentials only reach Lexful when a rotation policy is set to store there; connecting the integration alone doesn’t push anything.

Need Help?

If you should experience an issues or have any questions, please reach out to our support. You can view different ways to reach out here.