# BeyondInsight and Password Safe 25.1.1.389 (On-Premises only)

> 🚧 Important information
>
> This update is for On-Premises customers only. Fixes have been automatically applied to all 25.1 Password Safe Cloud deployments.

**February 19, 2026**

> ℹ️
>
> For a list of supported platforms for the latest version of BeyondInsight and Password Safe, see [Supported Platforms](https://docs.beyondtrust.com/bips/docs/ps-supported-platforms).

## :new: New features

This is a maintenance release.  There are no new features.

## :sparkles: Enhancements

This is a maintenance release.  There are no new enhancements.

## :hammer\_and\_wrench: Issues resolved

[block:parameters]
{
  "data": {
    "h-0": "Product Area",
    "h-1": "Description",
    "h-2": "Resolution",
    "0-0": "Endpoint Privilege Management",
    "0-1": "When an EPM agent checks-in, the IP Address for the corresponding Managed System may get reset to 127.0.0.1",
    "0-2": "If the EPM agent provides a loopback/127.0.0.1 IP Address, it is ignored by Password Safe.",
    "1-0": "Workforce Passwords Browser Extension",
    "1-1": "Updating a credential via the browser extension reports successful, however the credential is not updated.",
    "1-2": "Updates to credentials made from the browser extension are saved properly.",
    "2-0": "Workforce Passwords Browser Extension",
    "2-1": "Users with <Glossary>MFA</Glossary> configured cannot sign in to the Workforce Passwords Browser Extension.",
    "2-2": "The Workforce Passwords Browser extension now properly handles logins from users with MFA configured.",
    "3-0": "Public API",
    "3-1": "Attempting to retrieve a large number of secrets via the GET Secrets-Safe/Secrets API can fail with a timeout.",
    "3-2": "Increased the default client timeout.",
    "4-0": "Public API",
    "4-1": "When creating a new Active Directory user via the POST Users AP, the** Disable forms login for new directory accounts** configuration setting is ignored.",
    "4-2": "When creating new Active Directory users, the **Disable forms login** setting is properly applied.",
    "5-0": "API",
    "5-1": "When you use the **Invoke-Restmethod ** Windows PowerShell cmdlet to modify the permissions on a safe, performing a GET after a PUT results in a protocol violation error.",
    "5-2": "Corrected API response to align with proper RESTful conventions, which eliminates the protocol violation error in looped GET operations.",
    "6-0": "API",
    "6-1": "The GET Secrets endpoint defaulted the decrypt parameter to true, when it should default to false, and setting it to false would return a null owner email.",
    "6-2": "The GET Secrets endpoint now correctly defaults the decrypt parameter to false and returns the owner email in all cases when it’s available.",
    "7-0": "API",
    "7-1": "When you add an Active Directory user via the API and the **Disable forms** login where the new directory accounts checkbox is selected, the user setting is not disabled.",
    "7-2": "The **Disable forms** login for new directory accounts checkbox works as expected for new Active Directory users created from the API.",
    "8-0": "API",
    "8-1": "Field length validation discrepancy between POST and PUT public APIs for Text secrets, the PUT endpoint enforced a lower character limit than the POST.",
    "8-2": "The PUT endpoint has been updated to allow a Text secret with a value of up to **4096 **characters, to align with the limit on the POST endpoint.",
    "9-0": "SCIM API",
    "9-1": "Users created with SCIM API do not adhere to local account <Glossary>TOTP</Glossary> setting defaults.",
    "9-2": "Updated the SCIM API to adhere to local account TOTP setting defaults.",
    "10-0": "SCIM API",
    "10-1": "When making a call to retrieve **PrivilegedData** from the <Glossary>SCIM</Glossary> API, the returned values have the properties defined as **Name**, **Description**, and **Type**. As per the schema, these properties should be all lower case.",
    "10-2": "The <Glossary>JSON</Glossary> properties are now all in lower case.",
    "11-0": "SCIM API",
    "11-1": "SCIM **PrivilegedData** endpoint returned values have capitalized properties instead of lowercase.",
    "11-2": "Corrected the SCIM API so that calls to the **PrivilegedData** endpoint returns the properties in all lower case.",
    "12-0": "SAML",
    "12-1": "<Glossary>SAML</Glossary> login ignores the **Enable Group Resync** configuration option when user mapping is set to **Local** and always resyncs the local groups.",
    "12-2": "Groups are no longer resynced if the **Enable Group Resync** option is disabled.",
    "13-0": "SAML",
    "13-1": "When using a SAML configuration that uses **Active Directory** as the mapping type, if an Active Directory user gets created during a SAML login, that user is missing several user attributes. This includes the domain, email and first/last name, and can cause issues with mapping or attempting to remove the user.",
    "13-2": "All attribute data is now populated during SAML login.",
    "14-0": "SAML",
    "14-1": "User permissions may not be properly validated in some Microsoft Entra ID (Azure AD) SAML authentication scenarios.",
    "14-2": "Improved SAML session handling for Microsoft Entra ID (Azure AD) integrations to ensure user permissions are correctly enforced.",
    "15-0": "Smart Rules",
    "15-1": "AWS **Connector Instance** type retrieval and caching is exhibiting problems paging results, resulting in an infinite loop and, eventually, memory exhaustion, and, attempting to save a Smart Rule when the instance types \\< 1000 results in an error and the Smart Rule does not save.",
    "15-2": "The AWS **Connector Instance** type retrieval has been corrected to ensure appropriate execution and use of memory, and when there are more than 1000 instance types, Smart Rule now saves without an error.",
    "16-0": "Smart Rules",
    "16-1": "Google Cloud Platform (GCP) onboarding Smart Rule has a limit of 100 users.",
    "16-2": "Added support for onboarding more than 100 users using a Managed Account Smart Rule with a **Google Cloud Identity Query** filter.",
    "17-0": "Smart Rules",
    "17-1": "In some cases, high system usage is observed during processing of an asset onboarding Smart Rule.",
    "17-2": "Improved the underlying query performance that contributes to the processing of an asset onboarding Smart Rule.",
    "18-0": "Smart Groups",
    "18-1": "Using the Workgroup filter and creating a new Quick Rule may not include all items expected.",
    "18-2": "Corrected the selection process to ensure that all expected items are included.",
    "19-0": "Reporting",
    "19-1": "In some environments, the **Inactive Managed Accounts** report times out.",
    "19-2": "Excluded irrelevant records from the result set, resulting in much faster query execution time and improved report performance.",
    "20-0": "Reporting",
    "20-1": "The **Active Users** report only returns records with users that have been active within the last few months. The value in the parameter **Used In X Days** is not respected.",
    "20-2": "The **Used In X Days **report parameter is properly applied.",
    "21-0": "Reporting",
    "21-1": "When the **Password Safe Password And Session Activity** report is exported as a CSV, some cells may incorrectly contain line breaks, which causes a row to be split into two incomplete rows.",
    "21-2": "Line breaks from the **Reason** field are automatically removed.",
    "22-0": "Event Forwarding",
    "22-1": "When using a connector that uses the syslog format, the event severity in the priority field is the inverse of what’s expected for syslog events.",
    "22-2": "Syslog events are now sent with the correct severity.",
    "23-0": "Event Forwarding",
    "23-1": "Syslog event forwarder no longer sending application audit events.",
    "23-2": "Corrected the underlying event selection logic to ensure that all application events continue to be forwarded.",
    "24-0": "Mobile App",
    "24-1": "Secrets are not being properly returned to the mobile app from Secrets Safe personal folders when the user is a member of the Administrators group.",
    "24-2": "Users who are members of the Administrators group can now access secrets found in their personal folders.",
    "25-0": "Mobile App",
    "25-1": "An authentication error occurs when attempting to login via the Mobile App using an Active Directory or <Glossary>LDAP</Glossary> user account.",
    "25-2": "Active Directory and LDAP users can now successfully login via the Mobile App.",
    "26-0": "Sessions",
    "26-1": "RDP sessions using multiple monitors may encounter an error during session initialization.",
    "26-2": "RDP sessions with multiple monitors now function as expected.",
    "27-0": "Sessions",
    "27-1": "Poor performance with large scale datasets in the **Completed Sessions** Grid.",
    "27-2": "Made meaningful improvements in the data retrieval to improve performance and reduce grid loading time.",
    "28-0": "Directory Credentials",
    "28-1": "When using a directory credential with a username formatted as a <Glossary>UPN</Glossary>, directory queries using this credential do not work as expected.",
    "28-2": "Directory credentials with UPN usernames are now properly handled.",
    "29-0": "Propagation Actions",
    "29-1": "When trying to run a script propagation action on a managed system that uses a custom port, the propagation action fails.",
    "29-2": "The port setting on the managed system is now properly handled during propagation actions.",
    "30-0": "Functional Accounts",
    "30-1": "Local functional accounts on managed systems that have a <Glossary>DNS</Glossary> Name containing a period (.) are not properly tested via the Password Test Agent.",
    "30-2": "Local functional accounts are now tested properly.",
    "31-0": "Upgrade",
    "31-1": "In some scenarios, the upgrade to 25.1.0 could fail during the database upgrade if an asset is associated with invalid IP Address data.",
    "31-2": "The invalid IP Address data is adjusted to the latest data or reset if none exists.",
    "32-0": "Upgrade",
    "32-1": "Certain data points in existing environments (duplicate entries in Event Table Monitor, smart rules or smart rule criteria or actions with **Xen ** or **Risk ** in the names) could potentially cause a problem with the database upgrade process.",
    "32-2": "Made the database upgrade process more robust by adding additional safeguards around steps that remove or deactivate deprecated functionality.",
    "33-0": "SSH",
    "33-1": "<Glossary>SSH</Glossary> connection fails when using a DSS key for the login account",
    "33-2": "SSH connections now succeed when using a DSS key for the login account.",
    "34-0": "Activation Keys",
    "34-1": "In some rare cases, the **Activation Keys** page fails to load.",
    "34-2": "Improved the hostname resolution reliability to prevent this failure scenario from occurring.",
    "35-0": "BeyondInsight Configuration Utility",
    "35-1": "Several services were not started on the appliance after clicking **Apply **or after clicking **Start Services** in the BeyondInsight Configuration Utility.",
    "35-2": "The utility was updated to include those service starts in the **Apply **and S**tart Services** actions.",
    "36-0": "Omni Worker",
    "36-1": "A large backlog in the Event Forwarding queue can cause the service to stall.",
    "36-2": "The event forwarding logic has been updated to avoid the stall condition even when the backlog is very large."
  },
  "cols": 3,
  "rows": 37,
  "align": [
    "left",
    "left",
    "left"
  ]
}
[/block]

## :memo: Requirements

* Direct upgrades to 25.1.1 are supported from BeyondInsight versions 23.1 or later releases.
* BeyondInsight 25.1.1 supports SQL Server 2016 SP2 or higher.

## :spiral\_notepad: Notes

* This release is available by download for BeyondTrust customers (<https://beyondtrustcorp.service-now.com/csm>) and by using the BeyondTrust BT Updater.
* The MD5 signature is: 311d75ac58a9c8d2c75f9197c5000d48
* The SHA-1 signature is: 89dc7fa93be56719a6ad547d6bd51e55ba5eac59
* The SHA-256 signature is: 0f66439537ab9b3a4355e85c32426a24a2e7bcfcb88d8c66a8e71158b5fae45d