24 January 2022, 08:00
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.
Defender 6.2 is a minor release.
See New features.
New feature in Defender 6.2
Improved authentication UX for push notification: Enabling a seamless authentication experience for all clients (DDL, ISAPI, EAP), the authentication via push notification now happens automatically on Android and iOS devices. The user does not need to enter the 'push' keyword at the client login screen.
The following is a list of issues addressed in 6.2 release.
|
Resolved Issue
|
Issue ID |
|---|---|
|
DDL users when logging in with RDP, get "The password stored by Defender is no longer valid" error if the password is already saved |
289778 |
| Resolved Issue | Issue ID |
|---|---|
|
In certain configurations, Defender Management portal may unintentionally expose a privileged credential to an authenticated administrator |
270185 |
|
Defender admins face a considerable delay in programming a soft token in the larger environment |
277124 |
|
Users are unable to program Soft Token for Android from the management portal on Defender |
288146 |
| Resolved Issue | Issue ID |
|---|---|
|
As an end user when the authentication retry is triggered, the ''Invalid Windows password Enter a valid windows password'' error is intermittently seen |
285556 |
© ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center
