NetIQ SecureLogin 8.0 Service Pack 3 Release Notes

April 2015

NetIQ SecureLogin 8.0 Service Pack 3 (SP3) improves usability, and resolves several previous issues.

Many of these improvements were made in direct response to suggestions from our customers. We thank you for your time and valuable input. We hope you continue to help us ensure that our products meet all your needs. You can post feedback in the NetIQ SecureLogin forum on NetIQ Communities, our online community that also includes product information, blogs, and links to helpful resources.

The documentation for this product and the latest Release Notes are available on the NetIQ Web site in HTML and PDF formats on a page that does not require you to log in. If you have suggestions for documentation improvements, click comment on this topic at the bottom of any page in the HTML version of the documentation posted at the NetIQ SecureLogin documentation page. To download this product, see the NetIQ Downloads Web site.

NOTE:From this release onwards the release notes is not bundled with the SecureLogin installer. The release notes can be accessed from the NetIQ SecureLogin documentation page.

1.0 What’s New?

This release includes the following enhancement and fixed issues:

1.1 Support for Newer Versions of Mozilla Firefox Browser

In addition to Mozilla Firefox browser versions 19 to 34, this release supports Mozilla Firefox browser versions 35, 35.0.1, 36, and 36.0.1.

IMPORTANT:When you install SecureLogin 8.0 SP 3, install the supported Mozilla Firefox version first and then install SecureLogin. If you install SecureLogin before installing the supported Mozilla Firefox version, the SLoMoz add-on does not recognize those versions and an error for incompatible version is displayed.

When upgrading to this release, ensure that SLoMoz is enabled for the earlier versions of Firefox. Update the firefox version as per requirement and then upgrade to this release of NSL.

1.2 Software Fixes

This release of NetIQ SecureLogin includes the following enhancements and software fixes that resolve several previous issues:

Microsoft Excel 2013 Stops Responding When You Clear Filter on a Microsoft Excel Spreadsheet

Issue: In Microsoft Excel 2013, when you apply a filter and clear it, the CPU usage increases and the computer fails to respond for some time. This happens when SecureLogin interrupts an active .Net service.

This issue occurs only when you use Microsoft Excel 2013 with SecureLogin running in the background on your computer.

Fix: With this release of NetIQ SecureLogin, the DotNetFromWin32 registry setting is introduced to prevent computer from being unresponsive, and ensure that clearing a filter in Microsoft Excel 2013 does not lead to issues.For this fix to work, you must first disable the DotNet service and restart slproto then enable the following registry setting:

Location

Type

Name

HKLM/Software/Protocom/SecureLogin

Dword 32bit

DotNetFromWin32

For information about disabling the DotNet service, refer TID 7006772

Enabling the Password Protect the System Tray Icon Preference in a Standalone Mode Results in Authentication Error Even If You Enter the Correct Credentials

Issue: Enabling the Password Protection to System Tray Icon preference in a Standalone mode results in authentication error stating that the password or PIN is incorrect. This issue occurs when you upgrade SecureLogin from the version 8.0, 8.0 Service Pack 1 (8.0 SP1) to the version 8.0 Service Pack 2 (8.0 SP2) in a standalone mode with the Password protect the system tray icon preference enabled.

This issue occurs because SecureLogin does not decrypt the cache file.

Fix: With this release, NetIQ SecureLogin is able to decrypt the cache file.Users can use their network PIN/Password to authenticate, and the SecureLogin data is not lost.

SecureWorkstation Does Not Display Details of the Effective Policy

Issue: In SecureWorkstation’s main dialog box, when you click View Effective Policy, an error message stating that Secureworkstation does not have an active policy is displayed. The details of the policy are not displayed.

Fix: With this release, selecting the View Effective Policy displays the details of the policy. The users can manually configure the events by using Edit Events. For the updated policy to be effective, SecureWorkstation requires the user to log off and log in back on the workstation.

Cannot Log in to Computer Through Novell Logon

Issue: Users cannot log in to their computer by using the Novell logon tile, and the credential provider crashes displaying the Ctrl+Alt+Del screen. This issue occurs because SecureLogin, installed in Novell Client mode, sets the Registry Key for Novell Client login extensions, LoginExtType, incorrectly.

Fix: With this release of NetIQ SecureLogin, the installer updates the correct type and values of Novell Client login extensions for slina_c, slina_s components. The LDAPAuth component in the registry setting is now defined in the correct format. Hence, the Credential Provider does not crash when you log in to Novell Client.

LDAP Error 32 is Displayed When Authenticating in ADAM Mode

Issue: When you connect to LDAP through an ADAM instance, LDAP error 32 is displayed. This issue occurs when SecureLogin is Installed in Non-eDirectory LDAP mode using ADAM instance.

Fix: With this release, the LDAP error32 is not displayed during log in and LDAP authentication works fine in ADAM mode with the appropriate SSL port. For this fix to work, you need to use the LDAPCE utility to generate encrypted credentials and add it in the path, HKLM\Software\Protocom\SecureLogin as a String Key with the name LDAPContextlessSearchBindcreds.

For more information about encrypting the credentials by using LDAPCE utility, refer Using the LDAPCE Utility to Encrypt LDAP Credentials in the Installation guide. You can also enable Anonymous Bind in Active Directory and provide rights to anonymous users on the attributes that they need to browse.

SecureLogin Does Not Retrieve System Credentials and Error 426 is Displayed

Issue: When an eDirectory user logs in to the directory from a client machine through the Novell Client icon on the system tray, SecureLogin does not retrieve the system credentials for that user. Hence, when they use the sysuser and the syspassword variables to retrieve the credentials, SecureLogin displays an error stating, Sys variable not available. The application definition in SecureLogin cannot use these credentials in the single sign-on script. This issue is not observed if the user has logged in to the eDirectory through Novell Client logon tile on the Windows login screen.

Fix: With this release, SecureLogin retrieves the system credentials for the eDirectory users when they log in to eDirectory through either the Novell Client logon tile or the Novell Client on the system tray (from the desktop). SecureLogin can now use these system credentials for the application definitions.

The QWS3270 Secure Terminal Emulator is Not Added to the Configuration File (Tlaunch.ini)

Issue: The QWS3270 Secure terminal emulator is not added to Tlaunch.ini.

Fix: With this release, the QWS3270 Secure terminal emulator is added to Tlaunch.ini, and has appropriate pre-configured values for Emulator Path, Home Directory, HLLAPI DLL, HLLAPI Function and Session files.

2.0 System Requirements

For more information about hardware requirements, supported operating systems, and browsers, see the Quick Start Guide.

3.0 Installing or Upgrading to SecureLogin 8.0 SP3

You can either upgrade from the previous versions of SecureLogin or perform a new installation. For more information on upgrading from previous release, see Upgrading SecureLogin. For more information on installing SecureLogin, see NetIQ SecureLogin Installation Guide.

4.0 Known Issues

NetIQ Corporation strives to ensure our products provide quality solutions for your enterprise software needs. The following issues are currently being researched. If you need further assistance with any issue, please contact Technical Support.

4.1 Missing MADMAN Error is Displayed

Issue: When SecureLogin is modified by changing the mode from eDirectory to Active Directory, SecureLogin displays the Missing MADMAN error. (Bug 916614)

Workaround: To workaround this issue, select Seamless sign on using Windows Authentication when you modify the mode from eDirectory to Active Directory.

5.0 Contact Information

Our goal is to provide documentation that meets your needs. If you have suggestions for improvements, please email Documentation-Feedback@netiq.com. We value your input and look forward to hearing from you.

For detailed contact information, see the Support Contact Information website.

For general corporate and product information, see the NetIQ Corporate website.

For interactive conversations with your peers and NetIQ experts, become an active member of our community. The NetIQ online community provides product information, useful links to helpful resources, blogs, and social media channels.