Release Notes

Version 2.0.1.12

Previous Version: 2.0.1.0

Release Overview

PBA v2.0.1.12 delivers important stability improvements, enhanced security controls, improved smartcard and 2FA functionality, expanded hardware compatibility, and refinements to installation and upgrade workflows. This release focuses on strengthening authentication behavior, enforcing password policies, and improving overall system reliability.

Enhancements

• Added support for upgrade path from PBA 1.0.6.53+ to PBA 2.0.1.12 to streamline transitions.

• Enabled updating to a newer PBA version without requiring prior activation of the currently installed version.

• Added the ability to convert a primary drive to a secondary drive without reinstallation.

• Enhanced support for SIPR tokens.

• Improved Linux chainloading support with added flexibility

• Added support for enhanced smartcard PINs.

• Improved RAID support (contact your sales representative for required configuration information)

  • Added support for HBA350i controllers.

  • Added support for systems using Broadcom 9560 controllers.

  • Added support for GRAID RAID controllers.

Bug Fixes

• Resolved an issue allowing usernames longer than 40 characters during self-enrollment.

• Fixed an issue where users could be created with blank or space-only names.

• Corrected keyboard navigation issues preventing selection of Self-Enroll and Re-Enroll options.

• Corrected temporary password validation to properly enforce minimum length requirements (2FA).

• Corrected incorrect minimum password length values shown in error messages.

• Fixed a database error when modifying user email addresses.

• Resolved smartcard authentication failures following certain upgrade paths.

• Corrected an issue where re-activating a disabled PBA with bulk loader unnecessarily reinstalled the same version.

• Fixed installation failures on specific ARM-based platforms without a CMOS battery.

• Resolved a boot file scan failure on Rocky Linux systems.

• Fixed a software hang when re-enrolling an administrator account.

• Resolved login failures when upgrading from certain 1.x versions to early 2.x releases.

• Fixed errors occurring when using administrative flags during bulk load updates.

• Resolved installation failures when deploying systems with only preloaded SSDs.

• Improved smartcard detection reliability across customer environments.

1.0.6.30 ( Upgrade STRONGLY recommended )

1.0.6.26

Security Key authentication. Users can now choose to authenticate using a Security Key in addition to the existing methods of password and PIV/CAC. Security keys add a simple and widely available method of hardware authentication and can be configured to require a touch or PIN for added security.