NetIQ SecureLogin 8.6 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.
This release includes the following:
From this release, SecureLogin uses AES256 encryption as default encryption that provides higher security. For more information on how to set AES256 while Rights Assignment, see the following:
For Active Directory, see Assigning User Rights.
For Active Director Lightweight Directory Service, see ADAMconfig.exe and LDIFDE.exe.
For eDirectory, see Extending the eDirectory Schema.
From this release, SecureLogin is a Citrix Ready certified application. SecureLogin integrates with Citrix to provide a more efficient, simple, and reliable single sign-on solution. It provides a single login experience to users accessing Citrix Published Application, Published Desktop and other VDI environments. For more information on Citrix applications that are compatible with SecureLogin, see Citrix Ready Marketplace.
From this release, SecureLogin uses updated Lightweight Directory Access Protocol (LDAP) Software Development Kit (SDK). As part of updated LDAP SDK, SecureLogin LDAP server certificate validation is mandatory and it requires valid certificate configured on eDirectory server. Subject Name or Subject Alternative Name of the certificate must match with the SecureLogin LDAP server name.
NOTE:If Subject Name or Subject Alternative Name of the certificate does not match with the SecureLogin LDAP server name, SecureLogin LDAP connection to eDirectory fails. This issue also occurs if alias is used in place of Fully Qualified Domain Name (FQDN). For example, use the FQDN corp-eDir.microfocus.com in place of the alias corp-eDir.
This release includes the following software fixes:
SecureLogin Does Not Allow Big-IP Edge Client To Work Properly
SecureLogin Fails Does Not Provide Single Sign-on To SAPScript
SQL Manager Studio Fails To Start When SecureLogin Is Running
Sentinel Fails To Associate SecureLogin Events With Usernames
SecureLogin Does Not Specify Critical Information In the Correct Field of the Sentinel Collector
slNativeHost.exe Does Not Closes When Google Chrome Browser Is Closed
Issue: When SecureLogin is installed, Big-IP Edge Client fails to auto connect from windows login. (Bug 1036851)
Fix: With this release, slcredman.dll is modified to fix this issue.
Issue: SecureLogin fails to provide single sign-on to SAPScript because SecureLogin sends credentials in incorrect case. (Bug 1041736)
Fix: With this release, slWinSSO.dll is modified to fix this issue.
Issue: slTray.exe stops working when a startup script is used for applications. This issue also occurs when an application is deleted or its application definition is edited. This issue is fixed in this release. (Bug 1042694)
Issue: slbroker.exe stops working when std::wstring fails to allocate eight character length of string while using assignment operator function. This issue is fixed in this release. (Bug 1061912)
Issue: SQL Manager Studio fails to start when SecureLogin is running. It starts when SecureLogin is closed. (Bug 1077088)
Fix: Specify the required SQL Manager Studio files in exclude.ini list.
Issue: Sentinel fails to associate SecureLogin events with usernames that created these events. This issue occurs because the format used by SecureLogin to provide usernames in the InitUserName field is not recognized by Sentinel. (Bug 964508)
Fix: With this release, SecureLogin provides usernames in a format that is recognized by Sentinel.
Issue: SecureLogin provides all the required information to the Sentinel collector for event logging but, fails to specify this information in the correct fields. It causes Sentinel to fail to include the following critical information during event logging:
SecureLogin does not specify application name in the correct field of Sentinel collector. (Bug 964512)
SecureLogin does not specify event code in the correct field of Sentinel collector. (Bug 964515)
Fix: With this release, SecureLogin specifies the information in the correct fields of Sentinel collector.
Issue: A new slNativeHost.exe instance starts for every instance of Google Chrome browser. When Google Chrome browser is closed, the slNativeHost.exe instances keep running in background. (Bug 1027295)
Fix: From this release, the slNativeHost.exe instance is closed when Google Chrome browser closed.
For information about hardware requirements, supported operating systems, and browsers, see System Requirements for SecureLogin in NetIQ SecureLogin Quick Start Guide.
You can either upgrade from the previous versions of SecureLogin or perform a new installation. For information about how to install and how to upgrade, see NetIQ SecureLogin Installation Guide.
NetIQ Corporation strives to ensure our products provide quality solutions for your enterprise software needs. The following issues are currently researched. For release specific issues, see previous releases’ release notes. If you need further assistance with any issue, please contact Technical Support.
Issue: SecureLogin installation fails on Windows 8.1 and Windows Server 2012 R2 and the 0x80070017 - Data error (cyclic redundancy check) error is displayed. This issue occurs when the Windows is not updated. (Bug 1079485)
Workaround: Ensure that you have installed Windows Update (KB2919355)before you install SecureLogin.
Issue: SecureLogin displays the wxWidgets Debug Alert message and the SecureLogin manager administration console stops working when you import the .esx files that are created using older versions of SecureLogin to SecureLogin 8.6. (Bug 1070534)
Workaround: There is no workaround for this issue.
Issue: Java script exceptions are displayed when you try to add an application using the SecureLogin iManager plug-in. (Bug 1081199)
Workaround: Use slmanager to add applications.
Issue: The default port number and the event name of Advanced Authentication server are not displayed during the SecureLogin installation. (Bug 1079239)
Workaround: There is no workaround to display the default values. You can specify the Advanced Authentication server details.
Issue: When SecureLogin is running in Novell Client Mode, the SLmanager service does not save the changes that you make in the Corporate redirection settings. (Bug 1081340)
Workaround: Use iManager to change the Corporate redirection settings.
Issue: When you assign rights using adsschema.exe with AES Encryption option selected, SecureLogin displays the Error setting AES as default encryption for attriinfo_AES -2147016684 error message. This issue occurs when you assign rights on top level Domain (root). (Bug 1079971)
Workaround: Assign rights on organization units.
Issue: When SecureLogin is installed in the Active Directory mode and Citrix single sign-on is disabled, the SecureLogin pass-through feature does not provide the Active Directory credentials to the Citrix server. (Bug 1088843)
Workaround: Use the Citrix single sign-on to pass the Active Directory credentials to Citrix server.
Issue: When SecureLogin is installed in the Terminal Server Seamless Sign-on mode and the Microsoft Terminal Server Single Sign-on feature is disabled, the SecureLogin pass-through feature using Terminal Server Password Agent does not provide Active Directory credentials from Windows client to the Terminal server. It also disconnects the RDP connection to the server. (Bug 1088912)
Workaround: Perform the following steps to workaround this issue:
Remove the SecureLogin feature Terminal server Password Agent from the client system.
Use Microsoft Terminal Server Single Sign-on to pass the credentials from Windows client to the Terminal server.
Issue: When SecureLogin is installed in the Open Enterprise Server Client mode and a workstation only user logs in, the following issues occur (Bug 1088711):
SecureLogin fails to start but the SecureLogin processes start in background.
Sometimes, SecureLogin starts with a null user.
Workaround: There is no workaround for this issue.
For information about NetIQ legal notices, disclaimers, warranties, export and other use restrictions, U.S. Government restricted rights, patent policy, and FIPS compliance, see https://www.netiq.com/company/legal/.
© 2018 NetIQ Corporation. All Rights Reserved.
For information about NetIQ trademarks, see https://www.netiq.com/company/legal/. All third-party trademarks are the property of their respective owners.