Skip to main content

SAMO Security Manager - Release notes

10.0.2​

April 7, 2026

Changes since previous versionHelpDesk
Library upgrades
Dependency updates.
Stronger password hashing algorithm support added.
Refactor
Product renamed to SAMO Security Manager.

10.0.1​

February 4, 2026

Changes since previous versionHelpDesk
Refactor
Product renamed to SAMO Security Manager.
Build and release
Release artifacts renamed accordingly.

10.0.0​

January 14, 2026

Changes since previous versionHelpDesk
Technological upgrade
Application framework modernization.
Observability
Observability tooling integrated.
Library upgrades
Dependency updates.
Fixed bugs
Fixed inability to log into the administration console.
Session monitor bug fixed.
Endpoints
Additional service endpoints added.

Security server 1.13.0​

Optinal LDAP groups mappings

Security server is now not mapping LDAP groups (keeps current user groups intact) in case that no mappings are defined.

Security server 1.12.1​

Remeber me login option​

Security server now supports "remember me" login option

SAMOHD-4986 - Hour is not logged in 24h format​

Security server 1.11.1​

SAMOHD-4970 - LDAP synchronization is not working on MSSQL and Postgres​

This version is fixing ldap synchronization for mssql and postgres.

Security server 1.11.0​

Windows container​

Security server is since this version distributed also as windows server docker container.

Slow log support​

Gateway since this version supports logging of slow proxy-requests or db operations. Example configuration:

security.slowLog.controllers.enabled=true
security.slowLog.controllers.threshold=1000

security.slowLog.database.enabled=true
security.slowLog.database.threshold=1000

Or equivalent shortcut:

security.slowLog.*.enabled=true
security.slowLog.*.threshold=1000

It is recommended to setup slow logger in following way:

logging.slow.level=INFO
logging.slow.sendToRoot=false
logging.slow.writeToConsole=false
logging.slow.writeToFile=true

Security server 1.10.0​

Improved LDAP import logging​

Security is now on TRACE level logging all created/updated users

Optinal ldap import source base configuration​

All import sources can be now optinaly configured with

security.ldap.import.base

property

Security server 1.9.3​

fixed user permissions change on postgresql​

SAMOHD-4604

Security server 1.9.2​

user account lockout​

  • security server now supports account locking in case of too many wrong authentication attempts

    Example configuration (sec_config table):

    account.policy.lockoutDuration=900000
    account.policy.lockThreshold=15
    account.policy.counterResetAfter=120000

    Account will be locked after 15 wrong attempts for 15minutes. Attempts counter will reset in 2minutes.

  • Account can be unlocked manullay in user detail view by button "Unlock".

Security server 1.7.0​

samo-security 1.9.1​

  • fixed update of user street number

users & groups total count​

security server is now showing total count of filtered items

user enable/disable support​