NetIQ SecureLogin 8.1 Release Notes

December 2015

NetIQ SecureLogin 8.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 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.

1.0 What’s New?

SecureLogin 8.1 release includes the following:

1.1 Support for Google Chrome

This release provides the NetIQ Securelogin SSO Extension plug-in to support single sign-on for any application on a Chrome browser. Before using this plug-in, you must add the application definition for an application. You can add the application definition by using scripts or using the Add Application Definition wizard, when you launch the first instance of the application in Firefox or Internet Explorer.

To install the plug in, perform the following steps:

  1. Launch the Chrome web store.

    For more information about installing a plug-in from Chrome webstore refer, Chrome Webstore Help.

  2. On the left pane specify NetIQ Securelogin SSO Extension in the search field.

  3. Click NetIQ Securelogin SSO Extension and follow the on-screen prompts.

    If you require to develop websites locally then, select Allow access to file URLs under NetIQ SecureLogin SSO Extension. This will allow SecureLogin to login and fill form for local files such as file:///C:/dev/test.html.

NOTE:Single sign-on is supported on Google Chrome, but the application definition wizards are not supported.

1.2 Support for Windows 10

SecureLogin 8.1 is supported on Windows 10.

NOTE:SecureLogin does not support single sign-on for the following, on a Windows 10 computer:

  • Applications running on an Edge browser. However, you can use Internet Explorer 11, Firefox, and Chrome.

  • Any application that is installed from Microsoft Store.

  • Any Metro-style application that is used in conjunction with an active tablet mode.

1.3 Support for Newer Versions of Mozilla Firefox Browser

In addition to Mozilla Firefox browser versions 19 to 38, this release supports Mozilla Firefox browser versions 39 and 40.

IMPORTANT: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 SecureLogin.

1.4 Support for Active Directory Concurrent Connection

SecureLogin 8.1 supports limiting the concurrent connections of the Active Directory users in addition to the eDirectory users. For more information about limiting the concurrent connection of an Active directory user, see Limiting Concurrent Connections in the NetIQ SecureLogin Administration Guide.

1.5 Software Fixes

This release of NetIQ SecureLogin includes the following software fix:

SecureLogin Does Not Connect to LDAP Server After Resolving the Poodle Vulnerability Issue

Issue: When you resolve the poodle vulnerability by disabling the SSLV3 support, SecureLogin fails to connect to eDirectory and displays the following error:

Unable to contact LDAP server

This happens because SecureLogin works on SSLV3 support. (Bug 936660)

Fix: With this release, SecureLogin works with the TLS 1.0 support along with the SSLV3 support. So even when you disable SSLV3 support, SecureLogin can connect to the LDAP server.

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

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 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.2 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.3 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.4 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.5 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.6 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.7 SecureLogin Does Not Detect the Log in Dialog Box, or Identify the Screen for Single Sign-On

Issue: The single sign-on wizard does not identify the third party Java application named Syriusz, hence the wizard fails to identify the screen and other wizardable fields for single sign-on. (Bug 928541)

Workaround: To identify the Syriusz application for single sign-on, use the raw Keystrokes.

4.8 SecureLogin Does Not Support Switching Between Multiple Credential Set on the Syriusz Application

Issue: If multiple credential set is defined for a Syriusz application, SecureLogin does not allow switching between the multiple credential set. (Bug 928541)

Workaround: There is no workaround for this issue.

4.9 SecureLogin Fails to Start After Upgrading

Issue: SecureLogin fails to start and the error Unable to load access library moses.dll is displayed. This issue occurs only when you perform an upgrade and change the mode from NetIQ eDirectory with LDAP to NetIQ edirectory with Novell Client with SecretStore. (Bug 934655)

Workaround: To change the mode use SlmigrationHelper that is bundled with the installer.

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