NetIQ SecureLogin 8.1.1 Release Notes

May 2016

NetIQ SecureLogin 8.1.1 enhances the product capability 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 website 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 website.

1.0 What’s New?
1.1 Support for Advanced Authentication
1.2 Support for Contactless Smart Card in Desktop Automation Services
1.3 Software Fixes
2.0 System Requirements
3.0 Installing or Upgrading to SecureLogin 8.1.1
4.0 Known Issues
4.1 SecureLogin 8.1.1 Does Not Support Some of the Advanced Authentication 5.3 Features
4.2 SecureLogin 8.1.1 Repair Operation Doesn't Resolve the Corrupted Advanced Authentication Endpoint Registry
4.3 SecureLogin Modify Operation Does Not Modify the Advanced Authentication Configuration If Advanced Authentication Was Installed Already
4.4 SecureLogin Advanced Authentication Integration Does Not Work with the SecureLogin Re-Authentication <Default> Method
4.5 Re-Authentication Issues when Users Have the Same Username in Multiple Advanced Authentication Repositories
4.6 Closing SecureLogin Kiosk Login Prompt Does Not Clear the SecureLogin Sys Tray Footprints
4.7 A Message Endpoint session not found Is Displayed When the SecureLogin Advanced Authentication Endpoint Session Times Out
4.8 Google Chrome Does Not Allow Domain Authentication
4.9 The Enable Single Sign-On Dialog Box Launches Automatically Without Displaying Any Notification On Windows 10
4.10 An Error Message is Displayed When Installing the SecureLogin Plug-in In Mozilla Firefox 40
4.11 SecureLogin Manager Fails to Load the eDirectory Users and Objects After Changing the LDAP Secure/ Non-secure port in eDirectory
4.12 The Novell Client Service Fails to Start When Logging in to Windows with Default Context to the Novell Client Credential Provider
4.13 Missing MADMAN Error is Displayed
4.14 SecureLogin Displays an Error in Standalone Mode When the System Password is reset By Using Manage User Accounts
5.0 Legal Notices

1.0 What’s New?

SecureLogin 8.1.1 release includes the following:

1.1 Support for Advanced Authentication

This release integrates the SecureLogin infrastructure with Advanced Authentication features. This integration helps SecureLogin to single sign-on to the required application by using different authentication mechanisms.

1.2 Support for Contactless Smart Card in Desktop Automation Services

Now, the user can use contactless smart card in the SecureLogin Desktop Automation Services. The usage of this card enables instant login and logout ability for the users, in case any security issue arises. To use this card for authentication on DAS, you must install SecureLogin with the Advanced Authentication component. For more information about installing secureLogin with the Advanced Authentication component, refer Installing Advanced Authentication.

1.3 Software Fixes

This release of NetIQ SecureLogin includes the following software fixes:

Wizard does not detect fields on the taxport page

Issue: SecureLogin Wizard does not detect fields on the Taxport login page. It navigates the page using the keystrokes, and allows user to enter the Username and Password. It does not identify control fields and doesn't allow the user to enter any value in Domain. (Bug 958039)

Fix: With this release, the wizard is working successfully.

Java SSO fails when the Oracle server is upgraded.

Issue: When the Oracle server is upgraded, Java SSO failed thus leading to failure in the launch of Oracle forms (Bug 972368)

Fix: With this release, the Java SSO is working as expected.

SecureLogin terminates randomly when accessed through Microsoft Remote Desktop.

Issue: SecureLogin terminates randomly with error “An administrator has enabled and set the password on your account. For security reasons, as password options are available to you, SecureLogin requires you to login at least once with your password,” when accessed through Microsoft Remote desktop. (Bug 973734)

Fix: With this release, SecureLogin is not terminating and working as expected.

2.0 System Requirements

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

3.0 Installing or Upgrading to SecureLogin 8.1.1

You can either upgrade from the previous versions of SecureLogin or perform a new installation. For more information about 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 SecureLogin 8.1.1 Does Not Support Some of the Advanced Authentication 5.3 Features

Issue: SecureLogin 8.1.1 does not support the following Advanced Authentication 5.3 features:

  1. Advanced Authentication offline feature and SecureLogin offline login in the Kiosk environment.

  2. Advanced Authentication last logon tracking option.

  3. Advanced Authentication LDAP v3 support.

  4. SecureLogin Advanced Authentication kiosk login in the eDirectory mode.

  5. Citrix and Terminal server support with Advanced Authentication. (Bug 977564)

Workaround: No workaround is available.

4.2 SecureLogin 8.1.1 Repair Operation Doesn't Resolve the Corrupted Advanced Authentication Endpoint Registry

Issue: SecureLogin repair operation doesn't resolve Advanced Authentication registry corruption.(Bug 976540)

Workaround: Run the SecureLogin modify operation to un-install and re-install the Advanced Authentication component.

4.3 SecureLogin Modify Operation Does Not Modify the Advanced Authentication Configuration If Advanced Authentication Was Installed Already

Issue: SecureLogin modify operation doesn’t change the Advanced Authentication configurations if it was already installed. (Bug 976564)

Workaround: Execute the SecureLogin modify operation to remove Advanced Authentication feature, and then run the SecureLogin modify operation again to add this feature to include the new configuration.

4.4 SecureLogin Advanced Authentication Integration Does Not Work with the SecureLogin Re-Authentication <Default> Method

Issue: SecureLogin Advanced Authentication integration does not work with the SecureLogin re-authentication <default> method. (Bug 977163)

Workaround: Select the Advanced Authentication listed methods.

4.5 Re-Authentication Issues when Users Have the Same Username in Multiple Advanced Authentication Repositories

Issue: For users who have the same username in different Advanced Authentication repositories, re-authentication fails and displays the message Methods are not enrolled. (Bug 974768)

Workaround: Select configured repository and make that the default Advanced Authentication repository.

4.6 Closing SecureLogin Kiosk Login Prompt Does Not Clear the SecureLogin Sys Tray Footprints

Issue: When a user cancels the SecureLogin kiosk login prompt, SecureLogin sys tray footprints are not cleared from the Windows notification panel. (Bug 977561)

Workaround: Hover the mouse on the footprints.

4.7 A Message Endpoint session not found Is Displayed When the SecureLogin Advanced Authentication Endpoint Session Times Out

Issue: During SecureLogin kiosk smartcard login event, a message Endpoint session not found is displayed when the SecureLogin Advanced Authentication endpoint session times out after 60 minutes of inactivity. (Bug 977960)

Workaround: Click OK on Endpoint session not found dialog and try logging in again.

4.8 Google Chrome Does Not Allow Domain Authentication

Issue: When users access an application located on a specific domain by using Google Chrome, SecureLogin does not allow single sign-on to those applications. Users are required to manually provide the credentials. (Bug 935212)

Workaround: To workaround this issue, either enter the credentials manually or use Mozilla Firefox or Internet Explorer.

4.9 The Enable Single Sign-On Dialog Box Launches Automatically Without Displaying Any Notification On Windows 10

Issue: On a Windows 10 computer when SecureLogin detects an application for single sign-on, notification on the system tray is not displayed. But, the options for single sign-on are displayed in the single sign-on dialog box automatically. The application windows that are available to enable single sign-on does not get cached and the icon does not change the color.

Workaround: There is no workaround. If you do not require to enable single sign-on when an application is launched, close the dialog box. You need to re-launch the application to view the dialog box that prompts to enable single sign-on.

4.10 An Error Message is Displayed When Installing the SecureLogin Plug-in In Mozilla Firefox 40

Issue: When you enable SLoMoz 8.1.0, Mozilla Firefox 40 displays the following message when installing the SecureLogin plug-in:

SLoMoz could not be verified for use in Firefox. Proceed with caution.

This message is displayed because SLoMoz 8.1.0 is not listed in the Mozilla Firefox plug-in store.

Workaround: Ignore the warning and continue installation. You can use secureLogin without any issues.

4.11 SecureLogin Manager Fails to Load the eDirectory Users and Objects After Changing the LDAP Secure/ Non-secure port in eDirectory

Issue: SecureLogin Manager fails to load the eDirectory users and objects when the following conditions are true:

  • If SecureLogin is installed in the eDirectory LDAP mode

  • If the value of the LDAP secure, and unsecure port is not set to default in eDirectory

This issue occurs because SecureLogin uses the default LDAP ports to get access to eDirectory. So, if the value of the LDAP port is changed in eDirectory, SecureLogin cannot access eDirectory data.

Workaround: To workaround this issue, change the port number in the registry at HKCU\Software\Protocom\SecureLogin\LDAP Settings\NonSecureLDAPPort.

4.12 The Novell Client Service Fails to Start When Logging in to Windows with Default Context to the Novell Client Credential Provider

Issue: When you log in to Windows by using the Novell Client credential provider and if the eDirectory context is set to root, Novell Client fails to load and displays an error. This happens only when SecureLogin is installed on your computer. (Bug 948184)

Workaround: To workaround this issue, you must select the appropriate context of the user to log in to Windows.

4.13 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.

4.14 SecureLogin Displays an Error in Standalone Mode When the System Password is reset By Using Manage User Accounts

Issue: In standalone mode SecureLogin displays the error, Incorrect PIN/ Password. This issue occurs when the Password Protect system tray preference is enabled in the standalone mode and when you reset your user account password by using the Manage User Accounts option. (Bug 920964)

Workaround: To avoid error and data loss, it is recommended to change the password using the Ctrl+Alt+Del keys. This ensures that SecureLogin decrypts the updated password.