NetIQ SocialAccess is an appliance that simplifies a customer’s experience accessing resources on the Internet. Customers can use their credentials for an existing Internet account, such as Facebook or LinkedIn, to gain access to your business’ website. SocialAccess allows you to configure multiple identity sources that customers can use to authenticate to your website. SocialAccess creates a SAML assertion using attributes obtained from the identity sources to allow SAML authentications into the resources associated with your website.
This service pack 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 SocialAccess forum on NetIQ Communities, our online community that also includes product information, blogs, and links to helpful resources.
The documentation for this product is 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 SocialAccess NetIQ Documentation page. To download this product, see the NetIQ Downloads website.
The following sections outline the key features and functions provided by this version, as well as issues resolved in this release.
In this version, SocialAccess includes OpenSSL 1.0.1j, thereby removing the vulnerability to potential POODLE (Padding Oracle On Downgraded Legacy Encryption) attacks. For more information, see CVE-2014-3566. (Bugs 901709 and 903125)
SocialAccess includes enhancements and software fixes that resolve several previous issues.
SocialAccess provides improved localization of end user pages. Users can set their browsers to any of the following languages: English, Portuguese, French, Italian, German, or Spanish. Note, however, that the administration console does not currently provide support for languages other than English. (Bugs 901977 and 902539)
SocialAccess includes various usability improvements, as well as fixes for cosmetic issues that did not affect product functionality.
To update to SocialAccess 2.1.1, you must have an existing installation of SocialAccess 2.0 or 2.1. You can update an appliance to version 2.1.1 only through the update channel. Other upgrades are not supported. For more information, see Updating the Appliance
in the NetIQ® SocialAccess Installation and Configuration Guide.
For detailed information on hardware requirements and supported operating systems and browsers, see Installing SocialAccess
in the NetIQ® SocialAccess Installation and Configuration Guide.
To install SocialAccess, see Installing SocialAccess
in the NetIQ® SocialAccess Installation and Configuration Guide.
To update an appliance from SocialAccess 2.0 or 2.1 to version 2.1.1 through the update channel, see Updating the Appliance
in the NetIQ® SocialAccess Installation and Configuration Guide.
Perform the following steps to verify that the installation or update was successful.
Access the administration console at https://appliance_dns_name/appliance/index.html, then log in with the password specified during the initialization process.
Click the appliance, then click About. Verify that the version listed in the window is 2.1.1-build number.
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.
Issue: The Access Connector Toolkit does not currently provide a logout option, though the session does time out after 60 minutes of inactivity. (Bug 789303)
Workaround: Close the browser after you finish working in the Access Connector Toolkit.
Issue: During the appliance initialization process, changing the IP address from dynamic (DHCP) to static can cause an error stating that services are unavailable.
Workaround: This message can be ignored. Refresh your browser and the message disappears.
Issue: Appliance health might be green while user authentications fail. Basic network connectivity is working, but the identity source is not available. (Bug 798835)
Workaround: If user authentications fail, verify that you can access the social networking site outside of SocialAccess. If you cannot, the social networking site is down, and user authentications will continue to fail until the social networking site is available.
Issue: The connector definition fields in the Access Connector Toolkit include an Email check box for the persistent email attribute. You cannot currently change the persistent attribute to a different format, and SocialAccess does not attempt to map the persistent attribute unless you select the Email check box.
Workaround: To enable persistent logins, ensure that you select the Email check box in the connector definition.
Issue: If you implement custom branding in your SocialAccess environment and then re-run the initialization process to modify the DNS server or make other changes to an existing cluster, branding is reset to the default settings. (Bug 852663)
Workaround: This is the intended behavior in SocialAccess. Before you re-run the initialization process on an existing SocialAccess cluster, ensure that you back up your customized branding files so that you can reuse them.
Issue: In a version 2.0 cluster, nodes with dual NICs can have only a single DNS name and SSL keypair. In a version 2.1 cluster, nodes with dual NICs must have two DNS names and matching keypairs: one for the public network and one for the administration network. However, you must not configure the additional DNS name and associated keypairs for the two NICs until after you update all nodes in the cluster to version 2.1. After an update, in the Cluster Configuration window for a node, the Public Interface section shows the cluster’s old DNS name and the Administration Interface section is blank.
Workaround: After you update all nodes in the cluster from version 2.0 to version 2.1, you must manually configure the cluster DNS names and keypairs.
Log in as administrator to the administration console.
Click a cluster icon, then click Configure to open the Configure Cluster window.
In the Public Interface section, verify the Public DNS name and keypairs, or modify them as desired.
In the Administration Interface section, enter the Administration DNS name, then import the SSL keypair.
Click OK to save the new settings.
Click Apply to apply the settings to the cluster.
Issue: After you update a cluster from version 2.0 to version 2.1 and configure the DNS names and keypairs for the public and administration networks, users might not be able to access applications for connectors that use SAML-based single sign-on if the connector does not provide automatic configuration. Changing the Public DNS name or keypair can affect your existing connectors that provide SAML single sign-on.
Workaround: You must manually re-configure the affected SaaS applications to use the new URL and SAML certificate for the new Public DNS name and its associated keypair.
Issue: After you update a cluster from version 2.0 to version 2.1 and configure dual NICS to use two different DNS names and certificates for the public and administration networks, users might see the following SSL Handshake error when they click an appmark for a connector for Simple Proxy:
Server error! Error during SSL handshake.
Workaround: For each configured instance of the connector for Simple Proxy, you must open its Configuration page to allow it to detect the new settings for DNS names and certificates. After you update the connectors for Simple Proxy, users should no longer encounter the SSL Handshake error when they click the related appmarks.
Log in as administrator to the administration console for the appliance.
In the Applications panel, click the icon for an instance of the connector for Simple Proxy, then click Configure.
In the connector’s Configuration window, click OK.
Repeat Step 2 through Step 3 for each connector for Simple Proxy.
On the Admin page, click Apply to apply the changes for all connectors for Simple Proxy.
Wait to perform other administrative tasks until the configuration changes have been applied on each node of the cluster.
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 Web site.
For general corporate and product information, see the NetIQ Corporate Web site.
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.
THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT ARE FURNISHED UNDER AND ARE SUBJECT TO THE TERMS OF A LICENSE AGREEMENT OR A NON-DISCLOSURE AGREEMENT. EXCEPT AS EXPRESSLY SET FORTH IN SUCH LICENSE AGREEMENT OR NON-DISCLOSURE AGREEMENT, NETIQ CORPORATION PROVIDES THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. SOME STATES DO NOT ALLOW DISCLAIMERS OF EXPRESS OR IMPLIED WARRANTIES IN CERTAIN TRANSACTIONS; THEREFORE, THIS STATEMENT MAY NOT APPLY TO YOU.
For purposes of clarity, any module, adapter or other similar material (“Module”) is licensed under the terms and conditions of the End User License Agreement for the applicable version of the NetIQ product or software to which it relates or interoperates with, and by accessing, copying or using a Module you agree to be bound by such terms. If you do not agree to the terms of the End User License Agreement you are not authorized to use, access or copy a Module and you must destroy all copies of the Module and contact NetIQ for further instructions.
This document and the software described in this document may not be lent, sold, or given away without the prior written permission of NetIQ Corporation, except as otherwise permitted by law. Except as expressly set forth in such license agreement or non-disclosure agreement, no part of this document or the software described in this document may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, or otherwise, without the prior written consent of NetIQ Corporation. Some companies, names, and data in this document are used for illustration purposes and may not represent real companies, individuals, or data.
This document could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein. These changes may be incorporated in new editions of this document. NetIQ Corporation may make improvements in or changes to the software described in this document at any time.
U.S. Government Restricted Rights: If the software and documentation are being acquired by or on behalf of the U.S. Government or by a U.S. Government prime contractor or subcontractor (at any tier), in accordance with 48 C.F.R. 227.7202-4 (for Department of Defense (DOD) acquisitions) and 48 C.F.R. 2.101 and 12.212 (for non-DOD acquisitions), the government's rights in the software and documentation, including its rights to use, modify, reproduce, release, perform, display or disclose the software or documentation, will be subject in all respects to the commercial license rights and restrictions provided in the license agreement.
© 2014 NetIQ Corporation. All Rights Reserved.
For information about NetIQ trademarks, see http://www.netiq.com/company/legal/.