NetIQ SecureLogin 8.5 Service Pack 1 Release Notes

March 2017

NetIQ SecureLogin 8.5 Service Pack 1(SP1) 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?

SecureLogin 8.5 SP1 release includes the following:

1.1 Advanced Authentication Support

In addition to Advanced Authentication 5.4, this release supports Advanced Authentication 5.5 and 5.5.1. This release does not support Advanced Authentication 5.3.

NOTE: Before upgrading Advanced Authentication to 5.5.1 or modifying Advanced Authentication to use TLS 1.2, ensure the following:

  • The workstation must have .NET 4.5 or later installed.

  • SecureLogin must be upgraded to 8.5.1.

    If you have already upgraded Advanced Authentication to 5.5.1, SecureLogin upgrade fails. For the workaround, refer the Known Issues section.

1.2 Support for Windows Server 2016

This release extends support for Windows Server 2016.

NOTE:On Windows Server 2016, SecureLogin does not support Novell Client mode and Citrix and Terminal services.

1.3 Software Fixes

This release of NetIQ SecureLogin includes the following software fixes:

Launching SecureLogin 8.5 Through Windows Group Policy Editor Displays an Error

Issue: In a multi-domain environment, launching SecureLogin through Group Policy Editor displays Caught unhandled unknown exception; terminating. (Bug 1011692)

Fix: From this release, SecureLogin 8.5 launches successfully through Group Policy Editor.

Few Web Commands Do Not Work in Mozilla Firefox and Google Chrome

Issue: SecureLogin 8.5 scripts containing web commands such as SiteDeparted, Type, and Click does not work in Mozilla Firefox and Chrome browsers.(Bug 1013978)

Fix: From this release, all the web commands are working as expected in SecureLogin 8.5.

SecureLogin Crashes After Changing the Language

Issue: SecureLogin crashes when you change the language from an installed non-English language to a different non-English language. This issue occurs because the EN folder is not created when changing the language. (Bug 1021452)

Fix: From this release, SecureLogin 8.5 launches successfully after changing regional language.

Multiple User Entries are Added in the SecureLogin Registry

Issue: When a user logs in and logs out of SecureLogin without rebooting the system, multiple entries of the user is added in the registry HKLM\software\protocom\securelogin\volatile\All Users. (Bug 1015894)

Fix: From this release, the registry HKLM\software\protocom\securelogin\volatile\All Users is cleared during SecureLogin logout.

SLManager Does Not List all the Domains or Partitions in a Multi-Domain Environment

Issue: In SecureLogin 8.5, although you have configured two partitions of LDS instance or domains, SLManager lists only one partition or domain. (Bug 1011690)

Fix: From this release, slManager lists all the configured domains and partitions.

Delay in Launching .NET-Based Thick Client Applications

Issue: .NET based thick client application takes longer time to load in a workstation that contains SecureLogin.(Bug 929164)

Fix: From this release, there is no delay when loading .NET based thick client applications.

Launching Manage Logins Displays the wxWidgets Debug Alert

Issue: After modifying the preferences in the slManager that trigger data store upgrade, when you launch the Manage Logins the wxWidgets Debug Alert is displayed.(Bug 1022612)

Fix: In this release, wxWidegets alert does not appear when launching Manage Logins.

SecureLogin Does Not Identify Web Forms That Contain Only ID

Issue: SecureLogin does not identify the web form containing only id to perform single sign-on. (Bug 1025261)

Fix: From this release, SecureLogin identifies forms with id for single sign-on.

Changing the Data Store Version Does Not Work in SecureLogin 8.5

Issue: In SLManager, when you change the data store version of SecureLogin, the change is not updated.(Bug 1019487)

Fix: From this release, you can modify the datastore version from any lower version to a higher version but vice versa is not supported.

Using tsdiscon.exe in DAS Action File Does Not Switch User

Issue: In SecureLogin 8.5 DAS action file, if you have specified tsdiscon.exe as a log off action, DAS does not switch user.(Bug 1008422)

Fix: This issue is fixed in this release.

SecureLogin Does Not Launch on Citrix Published Desktop Startup

Issue: In Citrix published desktop, SecureLogin does not load automatically during startup even when SecureLogin is configured to load on startup.(Bug 1014958)

Fix: From this release, SecureLogin loads successfully on startup in Citrix published desktop.

SecureLogin in Standalone Mode Does Not Launch After Restarting Windows Server 2012 R2

Issue: In Windows Server 2012 R2, if you have SecureLogin installed in standalone mode SecureLogin does not launch after system reboot. This issue occurs because after reboot, SecureLogin in stand alone mode retrieves data from cache, which is disabled by default when you install SecureLogin on Windows Server 2012 R2.(Bug 1023019)

Fix: This issue is fixed in this release.

2.0 System Requirements

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

3.0 Installing or Upgrading to SecureLogin 8.5 SP1

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 about 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 researched in addition to the issues mentioned in NetIQ SecureLogin 8.5 Release Notes. If you need further assistance with any issue, please contact Technical Support.

4.1 SecureLogin 8.5.1 Does Not Support Some of the Advanced Authentication Features

Issue: SecureLogin 8.5.1 does not support the following Advanced Authentication features:

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

  2. Advanced Authentication LDAP v3 support.

  3. Citrix and Terminal server support with Advanced Authentication Device based login.

  4. Linked Authenticators.

  5. HTTP Proxy Server support.

  6. Non-Domain Joined Client support.

  7. Swisscom Mobile ID

  8. Multiple Enrollments

  9. Bluetooth Method

  10. Voice OTP Method

  11. PKCS#7

  12. Native LDAP Repository support

Workaround: No workaround is available.

4.2 Using Keystroke \Alt+\F4 to Close the Web Applications Does Not Work in Internet Explorer

Issue: If you have defined the keystroke as \Alt+\F4 to cancel the re-authentication, the web application does not close in Internet Explorer. (Bug 906118)

Workaround: To workaround this issue, specify \Ctrl+\w instead of \Alt+\F4 in the wizard script.

4.3 Copying SecureLogin Configuration By Using iManager 2.7.7 Displays an Error

Issue: When you copy the SecureLogin configuration from one object to another using iManager 2.7.7, the copy operation is successful but it displays page not found(404)error.(Bug 1026644)

Workaround: To workaround this issue, use iManager 3.0 or above.

4.4 SecureLogin 8.5.1 Upgrade Fails When Connecting to Advanced Authentication Server 5.5.1

Issue: Upgrade to SecureLogin 8.5.1 fails with an error when connecting to the Advanced Authentication server 5.5.1. This failure occurs because Advanced Authentication 5.5.1 uses TLS 1.2 by default and SecureLogin uses TLS 1.0 to connect with the server during upgrade.(Bug 1028859)

Workaround: To workaround this issue, enable TLS 1.0 in Advanced Authentication 5.5.1 server and perform SecureLogin upgrade. After the SecureLogin upgrade, you can disable TLS 1.0 in Advanced Authentication 5.5.1 server and use TLS 1.2 for subsequent connection.

4.5 Performance of SecureLogin and .NET Applications are Affected Intermittently

Issue: When you have a thick client .NET application and SecureLogin in the same system, performance of SecureLogin and other .NET applications are affected intermittently. This issue occurs because when you have a thick client .net application with several UI, it overloads the .NET worker in SecureLogin and affects the performance of SecureLogin.(Bug 1029683)

Workaround: To work around the issue, you must update the exclude.ini file periodically with the list of classes that must be excluded by SecureLogin.

Perform the following to update exclude.ini file:

  • Identify the class name of the form using the SecureLogin DOTNetWindowFinder utility.

  • Update the class names in the following format on the exclude.ini file available at C:\Program Files\NetIQ\SecureLogin:

    Classes
ClassName1
ClassName2