v3.2.1
IBM Verify SDK 3.2.1
Highlights
- Restores v2-compatible MFA signature key naming for new biometric and user-presence enrollments (#121)
- Improves on-premise MFA registration and refresh compatibility with IBM Verify Identity Access (#122)
- Refines device metadata collection and attribute mapping used in MFA flows (#123)
- Expands MFA test coverage and adds release documentation (#124)
Full release notes: 3.2.1
MFA compatibility updates
This release corrects signature key alias generation used during MFA enrollment so that new registrations align with the naming convention historically used by the v2 SDK line. This affects biometric and user-presence enrollment paths and improves interoperability with existing backend expectations.
On-premise MFA improvements
On-premise registration flows now better match IBM Verify Identity Access payload expectations, including:
device_rootedmapping for snake_case device security attributes- continued
deviceInsecureusage for cloud-oriented camelCase payloads - more consistent handling of
tenant_idin on-premise registration and token refresh scenarios
Device attribute refinements
MFAAttributeInfo has been improved to provide more accurate and efficient device metadata:
deviceNamenow prefers the user-configured device name and falls back toBuild.MODEL- root detection results are cached briefly to avoid repeated expensive checks
- static attributes are cached while
deviceIdcontinues to be refreshed from persistent storage for migration safety - biometric capability reporting is refined for face and fingerprint support
Build and release updates
- SDK version updated to
3.2.1 compileSdkupdated to 37- release notes added for 3.2.1
Full Changelog: 3.2.0...3.2.1