24 June 2024, 10:37
These release notes provide information about the One Identity Defender release.
Defender enhances security by using two-factor authentication to authenticate the users who request access to valuable resources within your organization. Defender uses your current identity store within Microsoft® Active Directory® to enable two-factor authentication, taking advantage of its inherent scalability and security, and eliminating the costs and time involved to set up and maintain proprietary databases. Defender’s Web-based administration and user self-service ease the implementation of two-factor authentication for both administrators and users.
See New features.
New feature in Defender 6.5.1:
Multi point authentication: With the latest update, users now have the flexibility to choose from multiple mobile service providers for SMS token authentication via the OneLogin portal. The default authentication option will be assigned to mobile providers configured within Defender.
The following is a list of issues addressed in 6.5.1 release.
|
Resolved Issue |
Issue ID |
|---|---|
|
Fixed an issue where high resource usage of CPU (up to 24 - 25%) with accounting Enabled in specific radius attribute. |
387617 |
|
Updated to latest Firebase HTTP v1 API, enhancing security measures to enable Push Notification functionality within the Defender Soft Token app |
421456 |
| Resolved Issue | Issue ID |
|---|---|
|
Update Log4j.dll to latest stable version |
452977 |
|
Update 7za and NewtonSoft.json to latest stable version |
414420 |
|
Update Log4net.dll to latest stable version |
414419 |
© ALL RIGHTS RESERVED. 使用条款 隐私 Cookie Preference Center
