NetIQ SocialAccess 2.2 Release Notes

March 2015

NetIQ SocialAccess 2.2 includes new features, 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.

1.0 What’s New?

The following section outlines the key features and functions provided by this version, as well as issues resolved in this release:

1.1 Supported Operating Systems

For information about the supported operating systems for the appliance, see Requirements in the NetIQ® SocialAccess Installation and Configuration Guide.

1.2 Improved Connector for NetIQ Access Manager

NetIQ has enhanced the integration between SocialAccess and NetIQ Access Manager 4.1.x to simplify the configuration. If you are using an older version of Access Manager, you must use the generic connector for NetIQ Access Manager. For more information about the enhanced connector for NetIQ Access Manager, see Configuring the Connector for NetIQ Access Manager in the NetIQ® SocialAccess Installation and Configuration Guide.

2.0 System Requirements

To upgrade to SocialAccess 2.2, you must have an existing installation of SocialAccess 2.0 or 2.1. You can update an appliance to version 2.2 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.

3.0 Installing SocialAccess

4.0 Verifying the Installation

Perform the following steps to verify that the installation was successful.

To check the installed version:

  1. Access the administration console at https://appliance_dns_name/appliance/index.html, then log in with the password specified during the initialization process.

  2. Click the appliance, then click About. Verify that the version listed in the window is 2.2-build number.

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

5.1 Changing from DHCP to Static IP During Initialization Causes Errors

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.

5.2 User Authentication Fails, but Health of the Appliance Is Green

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.

5.3 SAML 2.0 Inbound Users See Only Public Access Appmarks

Issue: When using the SAML 2.0 Inbound connector in mode Allow access for unknown users, after the first login when the user has just been created, the landing page displays only the Public appmarks. (Bug 920022)

Workaround: Since these specific types of users are not stored locally on the appliance, the appliance cannot apply the proper roles until the user logs in a second time. If you have any users that see this problem, instruct them to log out and log back in to the landing page. The landing page properly displays all of the appmarks.

5.4 Upgrade Issues

Manually Configure the DNS Names and Keypairs for Dual NICs After You Update the Cluster

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 or later 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. 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, you must manually configure the cluster DNS names and keypairs.

To configure the Public and Administration DNS names and keypairs for the cluster:

  1. Log in as administrator to the administration console.

  2. Click a cluster icon, then click Configure to open the Configure Cluster window.

  3. In the Public Interface section, verify the Public DNS name and keypairs, or modify them as desired.

  4. In the Administration Interface section, enter the Administration DNS name, then import the SSL keypair.

  5. Click OK to save the new settings.

  6. Click Apply to apply the settings to the cluster.

  7. Repeat Step 2 through Step 6 for each node in the cluster.

SAML-Based Single Sign-On Fails for Some Connectors After You Update a Cluster with Dual NICs

Issue: After you update a cluster from version 2.0 to version 2.1 or later 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.

Simple Proxy Users See an SSL Handshake Error After You Update a Cluster with Dual NICs

Issue: After you update a cluster from version 2.0 to version 2.1 or later 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.

To update the connectors for Simple Proxy:

  1. Log in as administrator to the administration console for the appliance.

  2. In the Applications panel, click the icon for an instance of the connector for Simple Proxy, then click Configure.

  3. In the connector’s Configuration window, click OK.

  4. Repeat Step 2 through Step 3 for each connector for Simple Proxy.

  5. On the Admin page, click Apply to apply the changes for all connectors for Simple Proxy.

  6. Wait to perform other administrative tasks until the configuration changes have been applied on each node of the cluster.

6.0 Contact Information

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.