Case-sensitive Passwords - Mitigating Risk in OnBase Upgrades - English - Foundation 22.1 - OnBase - Essential - Premier - Standard - external - Standard - Essential - Premier

Mitigating Risk in OnBase Upgrades

Platform
OnBase
Product
Mitigating Risk in OnBase Upgrades
Release
Foundation 22.1
License
Standard
Essential
Premier

Beginning with OnBase 12, administrators gained the option to enable case-sensitive passwords for a password policy. This option was configurable through OnBase 14. Beginning with OnBase 15, this option is no longer configurable and case-sensitive passwords are used by default.

If you are completing an IPUP for OnBase 11 to OnBase 15, note that once the database has been upgraded to version 15, users who change their passwords in the newer version Client will no longer be able to use the previous OnBase version. This is due to changes in how the password is stored in the database.

Users in a mixed-mode environment that need to access a version of OnBase previous to 12 with a database that has been upgraded to OnBase 15 can still change their passwords as long as the password is changed using the older OnBase Client. For example, if users change their passwords in version 11, they will still have a “legacy password” and can continue to log in to OnBase 11. As long as users are working in a single version of OnBase(for example, a user that always logs into OnBase version 11) then the implementation difficulty should be minimal. OnBase 15 accepts legacy passwords for authentication, so users with legacy passwords can log in to OnBase 15 clients as well.

If the password policy for the pre- OnBase 15 solution is configured with a change frequency of Require <n> Hours Between Changes or Expires Every <n> Days, it is recommended that your users change their passwords by using an older OnBase Client, or prior to upgrading the database.

For more information about legacy password usage, contact your first line of support.