- 13 Dec 2024
- 1 Minute to read
- Print
- DarkLight
- PDF
Axiad Conductor July 2024 Release Notes
- Updated on 13 Dec 2024
- 1 Minute to read
- Print
- DarkLight
- PDF
Last Updated: July 17, 2024
Release to Production Environments: July 17, 2024
Note
These notes are for the following Axiad Conductor product versions:
UCMS 4.18.1
Unified Portal 2.13
If you have any questions about these features or want to request a more in-depth discussion about the best way to leverage them, then reach out to us at productmanagement@axiad.com.
UCMS
New Features
Support for YubiKey Firmware 5.7
The YubiKey firmware version 5.7 brings a number of significant changes and improvements that are now supported by the personalization process that Axiad Conductor / UCMS uses to enable secure lifecycle management of the devices.
Axiad continues to support older YubiKey versions alongside the newer versions and this does not bring any breaking changes to your YubiKey experience.
Supported Versions
Currently, Axiad supports YubiKey firmware up to 5.7.1. Axiad will support newer versions of YubiKey in subsequent releases.
Bug Fixes
Ref ID | Description |
---|---|
PM-7334 | Errors returned by an IdenTrust CA during issuance or revocation will now produce a more explicit message |
PM-7495 | You can now edit a workflow even if there is not an active credential profile is associated to it |
PM-7497 PM-7582 | Migrating a user and renewing one of their devices will no longer result in duplicated device records |
PM-7586 | After upgrading from UCMS 4.13 to 4.17, searching for a user in the helpdesk or scanner will no longer result in UCMS.devices.internalError error |
PM-7704 | The UPN can now be included as a SAN extension in encryption certificates issued by MSCA |
PM-7617 PM-7321 PM-7513 | Update PIN settings to meet MD930 requirements |
PM-7672 | UCMS Operator email address can now include “-” and “_” following “@” |
PM-7898 | Reset PIN supported for Gemalto cards |
PM-6594 | SMTP support enhancements |
Unified Portal
Enhancements
Device Expiration Notifications Options
Operators can now choose if they want Axiad to send notifications to expired devices or not.
Configuration Change
To disable Device Expiration Notifications, you must request the change. Please contact your Customer Service Representative or email customer.success@axiad.com.
Bug Fixes
Ref ID | Description |
---|---|
PM-7335 PM-7787 PM-7788 | Axiad displays a meaningful error message if backend services are unreachable |
PM-7905 | When configuration leads to a mismatch, Axiad fails the issuance and displays necessary information for the user |
PM-8125 | Error message updated when issuance fails due to unsupported device or invalid PIN to be more helpful. |