Release Date: September 29, 2025
A2A
Product Updates
| Item | Description |
|---|---|
| SSGR-6501 | Added the ability to link Access Policies to A2A application authorizations. This allows an entire access policy to be associated with an application instead of listing credentials one by one, ensuring applications adhere to the same rules as users and simplifying migrations from other PAM solutions. |
DevOps Secret Manager
Translation Fixes
| Item | Description |
|---|---|
| SSGR-7440 | Fixed a translation issue in DevOps Secret Manager where the "Create Template" button was always displayed in English. The button is now correctly translated based on the user's selected language. |
Product Updates
| Item | Description |
|---|---|
| SSGR-3594 | Added new columns for traceability in API logs reports in the DSM module: "Code Authorization", "Environment", and "System". The new feature allows better identification of executions, associating them with corresponding systems and environments. |
Domum Remote Access
Bug fixes
| Item | Description |
|---|---|
| SSGR-7465 | Fixed an issue where the Name field would become blank for limited users created via Azure SCIM after any attribute of the Azure user was updated. |
| SSGR-7378 | Fixed an issue where it wasn’t possible to delete limited internal users from a group in Domum. |
| SSGR-7295 | Fixed an issue where, in Domum’s monitoring center, the buttons to livestream, display the details of the session, and end the session weren’t clickable. |
| SSGR-7478 | Fixed an issue where, when deprovisioning an user on Azure via SCIM protocol, the user wasn’t being deactivated in Domum. |
EPM Client Manager
Bug fixes
| Item | Description |
|---|---|
| EPM-967 | Removed the SHA-1 option from the File Hash criteria in the EPM for Windows access lists, as this algorithm is deprecated. |
| EPM-951 | Fixed a bug on the EPM dashboard where the usage chart was not displaying any information. The chart now correctly populates with EPM usage data. |
EPM Linux
Bug fixes
| Item | Description |
|---|---|
| EPM-909 | Fixed an error in EPM for Linux that occurred when configuring rules for the {{systemctl}} command through access policies and sudo rules. The configuration now works as expected. |
EPM MacOS
Bug fixes
| Item | Description |
|---|---|
| EPM-947 | Fixed backend hostname update so the device hostname is refreshed on every EPM macOS registration. |
| EPM-949 | Fixed an issue in EPM macOS where the last policy synchronization timestamp was not displayed. |
MySafe
Bug fixes
| Item | Description |
|---|---|
| SSGR-7496 | Fixed the behavior of global search in MySafe, which displayed data from other users when searching for terms found in password or file names. Results are now shown only when they belong to the logged-in user's own vault. |
MySafe extension
Bug fixes
| Item | Description |
|---|---|
| SSGR-6611 | Added option to disable the automatic context menu in the MySafe Browser Extension. The extension now has this feature turned off by default and it can be manually enabled in the settings according to the user’s preference. |
Orbini/Orbit
Product Updates
| Item | Description |
|---|---|
| SSGR-3213;TCS-2983 | Added an option to register custom SAML and OpenID providers with configurable name and logo. |
Bug fixes
| Item | Description |
|---|---|
| SSGR-7473 | Fixed an issue where email and Syslog settings in the Orbit Server Manager would become corrupted after an environment update. The configurations are now correctly preserved across updates |
PAM - Credential Management
Product Updates
| Item | Description |
|---|---|
| SSGR-7357 | Improved the display of results from the global search, identifying available actions for the credential, the device related to the credential, as well as enabling access to reports directly from the results. |
| SSGR-7399 | Improved usability in the credential report actions, which will now display buttons for the main actions on the record row. |
Bug fixes
| Item | Description |
|---|---|
| SSGR-7460 | Fixed the error where a credential associated with a disabled device was not deactivated. Now when the device is disabled, its associated credential is also deactivated. |
| SSGR-7388 | Fixed the error where the Credential Owner field wasn't displayed when data was imported in bulk via a spreadsheet. |
Translation Fixes
| Item | Description |
|---|---|
| SSGR-6374 | Corrected the translation of the message on the JIT credential provisioning screen. |
PAM - Session Management
Product Updates
| Item | Description |
|---|---|
| SSGR-7397 | Improved usability of the Access Panel screen, making it easier to identify the information available on screen. |
| SSGR-7448 | Added new connectivity for “DB2” with default port “50000”. |
Bug fixes
| Item | Description |
|---|---|
| SSGR-7298 | Fixed the error where RemoteApp automations with more than 44 actions were not loading. |
| SSGR-7294 | Fixed drag and drop for items in the script field when editing a RemoteApp |
| SSGR-7660 | Fixed the error in SSH Proxy sessions that displayed a date format error message when using a credential with a justification registered in the Access Policy. |
Translation Fixes
| Item | Description |
|---|---|
| SSGR-7403 | Altered the name "All" to “All credentials” on the PAM home. |
Settings
Bug fixes
| Item | Description |
|---|---|
| SSGR-7370 | Fixed an issue configuring a user’s token with a newly registered MFA provider. |
| SSGR-7344 | Fixed an authentication issue when using MFA with Cisco Duo Security. |
| SSGR-6416 | Fixed a display issue in dark mode where the names of inactive modules were unreadable due to poor contrast. The text is now clearly visible. |
Product Updates
| Item | Description |
|---|---|
| SSGR-6425 | Improved the web SSO flow by unifying login and SSO on a single screen. |
| SSGR-6821 | Removed the space between the checkbox and the column in the Domain section on the System Parameters screen, improving the presented layout. |
| SSGR-7355 | Implemented the standard that, upon first login in Segura®, the screen displayed will be the PAM Core Home. Subsequent logins will continue to follow the standard of opening on the last screen used. |