Chat now with support
Chat with Support

Defender 5.9.6 - Release Notes

Release Notes

One Identity Defender 5.9.6


Release Notes

Friday, February 7, 2020

These release notes provide information about the One Identity Defender release.


About Defender

About One Identity Defender 5.9.6

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.

Deprecated features

Deprecated features in Defender 5.9.6:

  • Removal of integration of Cloud Access Manager (CAM) section Removed the integration of CAM section from the documents.

See also:

Resolved issues

Resolved issues

The following is a list of issues addressed in 5.9.6 release.

Table 1: Defender Desktop Login resolved issues

Resolved Issue


Issue ID

Offline cache data is not updated after logging in to corporate VPN.


Delayed log on observed on Windows 10 when logging in from outside of the network.


Defender Desktop Login does not try to search for the available DCs or GCs in the forest.


User authentication to Defender Desktop Login using Google Authenticator tokens that are prefixed with PIN fails, when Defender Service is unavailable.


When a user authenticates to a Windows 10 system via Defender Desktop Login, the logon process is delayed.


Table 2: Defender Management Portal resolved issues
Resolved Issue Issue ID

When Defender Administrator searches for a user in the Management portal, username does not appear in the header.


Unable to schedule the Defender reports.


When Defender Management Portal is installed with a non-Domain Admin Group as the default administrator group of the Management Portal, and a user who is member of the non-Domain Admin Group logs in to the Management Portal, then the Administrator privileges are not provided to the user.


When User search is performed using Defender Management Portal, a delay is seen while retrieving User Properties.


Self-service User is unable to request for Software Tokens from the Defender Management Portal.



Table 3: Defender Security Server resolved issues
Resolved Issue Issue ID
The DSS Service restarts when a username consists of special characters and exceeds the defined character limit. TFS792148
Authentication is abandoned when a user authenticates through VPN. TFS795681/TFS796768
Defender Security Server service crashes if the SMTP server is not available. TFS796950
When Defender Security Server is configured to use SSL port 636 and server is rebooted, the DSS service fails to start. TFS802183
When a User is assigned with an email or an SMS token along with an Authy token, the email or SMS is not sent to the User. TFS800967

DSS Audit logs display incorrect Active Users count.


DSS Audit logs capture GC connections repeatedly.


YubiCloud tokens are not working with Defender.



Table 4: Defender Soft Token for Java resolved issues
Resolved Issue Issue ID

When you attempt to run the Soft Token for Java with Java 9 or later installed on the system, you encounter the following error:

ClassCastException: class jdk.internal.loader.ClassLoaders$AppClassLoader cannot be cast to class (jdk.internal.loader.ClassLoaders$AppClassLoader and are in module java.base of loader 'bootstrap').



Table 5: Other resolved issues
Resolved Issue Issue ID

Authentication using Temporary Tokens for Defender Soft Token for Android fails.


Authentication using Temporary Tokens for Defender Soft Token for iOS fails.


Authentication using Temporary Tokens for Defender Soft Token for Windows fails.


In the Defender Administration Console, Administrator is not able to set PIN for tokens.


The Active Roles Web interface does not allow assigning Soft Tokens for iOS for users.


Time-based non-OATH iOS tokens generate invalid responses when an expiry date is set for the token activation code.


In Active Roles Web interface, when a user assigned with Defender-Administrator Access template tries to program Defender tokens, a permission related error message is displayed.


Diagnostic logging for Integration Pack for Active Roles display token activation Code when programming token via Active Roles Console.


When Defender Soft Token for iOS is programmed with an expiration date, Token Properties are not updated correctly in Administration Console.


After you install Microsoft July 2018 Security and Quality Rollup updates for .NET Framework updates, an error is displayed when you view Defender Properties in the Active Roles Web Interface.


The Done and Swipe buttons in Defender Soft Token for iOS have UI issues on the iPhone XS Max device.


Unable to delete GrIDsure Token/Defender Password from a User when the name contains forward slash.


User is able to login to the clients only with Active Directory password even after completing the token registration.


YubiCloud fails to validate the token response.


Self Service Tools
Knowledge Base
Notifications & Alerts
Product Support
Software Downloads
Technical Documentation
User Forums
Video Tutorials
RSS Feed
Contact Us
Licensing Assistance
Technical Support
View All
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating