Skip to main content

LastPass connector

Back to the connector overview, authentication methods, and actions.
17 Sept 2026
data-syncAdded scheduled data sync to four list actions — users, groups, organizations, and roles — so these collections can be kept in sync and read back without calling LastPass on every request. Each refreshes in full on every run, since the LastPass Provisioning API has no updated-since filter to drive incremental sync.
lastpass_unified_list_groups, lastpass_unified_list_organizations, lastpass_unified_list_roles, lastpass_unified_list_users
27 Aug 2026
bug-fixFixed several unified IAM issues, including mismatched release stages between list and detail actions, missing role scope information, an organization not-found error, incomplete group membership data, and invalid credentials reporting a not-found error instead of an authentication error.
lastpass_unified_get_group, lastpass_unified_get_me, lastpass_unified_get_organization, lastpass_unified_get_role, lastpass_unified_get_user, lastpass_unified_list_groups, lastpass_unified_list_organizations, lastpass_unified_list_resource_types, lastpass_unified_list_resource_users, lastpass_unified_list_roles, lastpass_unified_list_users
22 Jul 2026
bug-fix connection-guideFixed the connection test so invalid credentials are rejected — the LastPass Provisioning API returns HTTP 200 with an error body for a wrong account number or provisioning hash, so the get_user_data test action now maps that response to a 401 instead of connecting successfully. Rebuilt the config connection guide with live Admin Console screenshots covering the Advanced > Enterprise API navigation, the account number, and the provisioning hash creation and copy steps, and corrected the Account Number (CID) field description to point to the Advanced > Enterprise API page.
lastpass_get_user_data
13 Jul 2026
bug-fixFixed unified IAM credentials, organizations, roles, resource users, and users actions that shipped raw or malformed data despite declaring correct field mappings, plus a decorative resource_id filter and expand input.