OVERLAPS Update 3.3.0 (SAML Project)

After a long and arduous development period, I am happy to finally be able to announce that update 3.3.0 is now available for download. Now featuring SAML Single Sign-On support, you can hand over user authentication to third-party services such as AD FS, Entra, or Okta, and enjoy the added benefits those providers bring to your security and user experience.

Where can I read more about the SAML support in OVERLAPS?

We’ve updated the documentation with information on how to setup both your Identity Provider (IdP) and OVERLAPS so that they work together to provide secure authentication. You can read about it here:

https://int64software.com/overlaps/docs/installation-and-configuration/setting-up-saml-authentication

Where can I get the update?

The update is available to download from your “My Account” page on the main OVERLAPS website:

https://int64software.com/overlaps/my-account

Full Change Log

• Added SAML Single Sign-on authentication support, see the documentation for setup information.
• Added the option to disable the login form like the one to disable WIA.
• Fixed a null reference exception when searching for computers that don’t exist.
• Added an option to the Group Refresh operation called “GroupUpdateMaxParallelism” which controls how many CPU threads a full Group Refresh uses. By default this is set to 10, but the operation will actually be limited to the number of cores on the server’s CPU if it is less than this. However you can set it lower if you’re, for example, running across domains located in different global locations and you want to limit the traffic or are having timeout issues. Alternatively, if your server has a lot of cores and you want to process a lot of groups faster, you can increase this up to 256.
• Added a report for viewing a computer’s password history which enables looking up devices which no longer exist in Active Directory.
• Fixed an issue where the MFA “Maximum Days to Remember Devices” setting couldn’t be set to the maximum number of days for that setting. Also increased the maximum to 365 days.
• Added an API version to the program update retrieval process to allow for schema changes in the future.
• Replaced reliance on Google Charts for generating QR Codes when activating Two Factor Authentication with an internal JavaScript method instead.
• Fixed the “Computers with an expired LAPS password” report which may have missed some devices under certain circumstances.
• Added pagination to all reports to reduce server load and improve performance.
• Added an easier way to control results in the “Computers with an expired LAPS password” report so you can now set a minimum starting date to help filter out recent expiries.
• Fixed a bug in the method responsible for updating user display names during login.
• Updated Dependencies:
  BouncyCastle => 2.4.0.33771
  CsvHelper => 32.0.3.22
  Log4Net => 2.0.17.0
  MailKit and Mimekit => 4.6.0.0
  SQLite => 1.0.118.0
  Vanara Core => 4.0.1.0