Capabilities
The LastPass connector supports automatic account provisioning and deprovisioning. New accounts are created with an email invitation to activate LastPass. Deprovisioning permanently deletes the LastPass account and its vault data; to block access while keeping the vault, use the disable_user action instead.
Group provisioning adds and removes users from LastPass groups. Only users can be added to groups.
Groups with no members don’t appear in C1. LastPass only reports groups that have at least one member, so a group disappears from C1 after its last member is removed and comes back once someone is added in LastPass.
Shared folder access is read-only. The LastPass Enterprise API has no way to add or remove shared folder members, so C1 syncs shared folder access but can’t provision it.
Connector actions
Connector actions are custom capabilities that extend C1 automations with app-specific operations. You can use connector actions in the Perform connector action automation step.
Configuring the connector requires you to pass in information from LastPass. Gather these configuration details before you move on.
Here’s the information you’ll need:
- LastPass CID
- LastPass Provhash
Permissions for provisioning: The provisioning hash gives full Enterprise API access, including creating, deleting, enabling, and disabling users and changing group membership. Anyone with the hash can make these changes regardless of their Admin Console role, so store it as a secret.
See the LastPass docs for information on how to acquire credentials: View the documentation
To complete this task, you’ll need:
- The Connector Administrator or Super Administrator role in C1
- Access to the set of LastPass configuration information gathered by following the instructions above
Follow these instructions to use a built-in, no-code connector hosted by C1.In C1, navigate to Apps > Connectors and click Add connector.
Search for LastPass and click Add.
Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.
Set the connector’s Name and, optionally, a Description.
Click the pencil icon next to Owners to choose who can configure and manage this connector.
Click Add. The connector is created and its configuration page opens.
Find the Settings area of the page and click Edit.
Enter the configuration information from the previous section.
The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.
Follow these instructions to use the LastPass connector, hosted and run in your own environment.When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1 UI for access reviews and access requests.Resources
Contact C1’s support team to download the latest version of the connector.Step 1: Set up a new LastPass connector
In C1, navigate to Apps > Connectors and click Add connector.
Search for Baton and click Add.
Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.
Set the connector’s Name and, optionally, a Description.
Click the pencil icon next to Owners to choose who can configure and manage this connector.
Click Add. The connector is created and its configuration page opens.
In the Settings area of the page, click Edit.
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 LastPass connector deployment:Secrets configuration
See the connector’s README or run --help to see all available configuration flags and environment variables.Deployment configuration
Step 3: Deploy the connector
Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.
Check that the connector data uploaded correctly. In C1, click Apps. On the Managed apps tab, locate and click the name of the application you added the lastpass connector to. lastpass data should be found on the Entitlements and Accounts tabs.
