IBM Single Sign On for Bluemix Version 2.0. Identity Bridge Troubleshooting topics

Transcription

1 IBM Single Sign On for Bluemix Version 2.0 Identity Bridge Troubleshooting topics

2

3 IBM Single Sign On for Bluemix Version 2.0 Identity Bridge Troubleshooting topics

4 ii IBM Single Sign On for Bluemix Version 2.0: Identity Bridge Troubleshooting topics

5 Contents Figures v Tables vii Chapter 1. Getting started with troubleshooting Messages Message format Message identifiers Logs Using the Messages topics to resolve errors Searching knowledge bases Getting fixes Getting fixes from Fix Central Contacting IBM Support Exchanging information with IBM Sending information to IBM Support Receiving information from IBM Support Subscribing to Support updates Index Chapter 2. Known issues and solutions 3 Chapter 3. Known limitations Chapter 4. Deploying pending changes 11 Chapter 5. Support Information Techniques for troubleshooting problems iii

6 iv IBM Single Sign On for Bluemix Version 2.0: Identity Bridge Troubleshooting topics

7 Figures v

8 vi IBM Single Sign On for Bluemix Version 2.0: Identity Bridge Troubleshooting topics

9 Tables vii

10 viii IBM Single Sign On for Bluemix Version 2.0: Identity Bridge Troubleshooting topics

11 Chapter 1. Getting started with troubleshooting Problem determination, or troubleshooting, is a process of determining why a product is not functioning in the expected manner. These topics provide information to help you identify and resolve problems with IBM Single Sign On for Bluemix. The troubleshooting process, in general, requires that you isolate and identify a problem, then seek a resolution. You can use a troubleshooting checklist to help you. If the checklist does not lead you to a resolution, you can collect additional diagnostic data and analyze it yourself. You can also submit the data to IBM Software Support for analysis. Note: In addition to these topics, use the topics that describe how to troubleshoot the IBM Security Access Manager appliance. These topics describe how to troubleshooting the appliance functions that are common to all activation levels of IBM Security Access Manager. See Troubleshooting the Access Manager appliance Messages All messages issued by IBM Single Sign On for Bluemix adhere to a Message Standard. The Message Standard specifies a standard format for all messages issued by this product. The standard, based on the IBM Message Standard, is intended to provide a consistent and meaningful way for identifying messages across the entire IBM product set. Messages issued by IBM Single Sign On for Bluemix, along with detailed explanations and suggested actions, can be found in the Messages section of the IBM Single Sign On for Bluemix Knowledge Center. Message format A message consists of a message identifier (ID) and message text and an error code. The error code is a unique 32-bit value. The error code is either a decimal or hexadecimal number and indicates that an operation was not successful. All messages that follow the message standard are listed in the Messages section of the Knowledge Center. Each of these messages has a detailed explanation and suggested actions. Message identifiers A message ID consists of 10 alphanumeric characters that uniquely identify the message. The message ID consists of the following parts: v A 3-character product identifier. v A 2-character component or subsystem identifier v A 4-digit serial or message number v A 1-character type code that indicated one of the following message severities: W Warning E Error 1

12 I Information Logs Use log files to retrieve information about a problem in your environment. Enable the collection of detailed log and trace information to troubleshoot problems. You can collect and review standard informational log messages or detailed trace messages to help determine the root cause of a problem. For information about viewing event logs, see Viewing the event log. For information about viewing the appliance log files, see Viewing application log files Using the Messages topics to resolve errors Use the unique message ID associated with a message to locate detailed explanations and suggested operator responses in the guide. The Messages section of the Knowledge Center contains a list of messages in the logs, graphical user interfaces, and the command line. For example, if you see the following error message in the message log: CTGSI0311E The distributed session cache server was unable to generate a new key. Search for CTGSI0311E in the guide for information about why the error occurred and how to resolve it. For example, the previous error message has the following information in the Messages section of the Knowledge Center: Explanation: The distributed session cache server was unable to generate a new key. Administrator response: Examine the distributed session cache server logs for further details. It may be necessary to restart the distributed session cache server completely to correct this condition. 2 IBM Single Sign On for Bluemix Version 2.0: Identity Bridge Troubleshooting topics

13 Chapter 2. Known issues and solutions Determine if an issue you are having has a fix or a workaround. Enabling Compatibility View in Internet Explorer 9 returns the Browser not Supported message The IBM Security Access Manager appliance does not support the browser operating in this mode. The following message is displayed in the local management interface: Browser not Supported. The IBM Security Access Manager appliance does not support this browser. The following browsers are currently supported: - Internet Explorer 9 or later - Firefox 17.0 or later - Google Chrome 27.0 or later Solution: The appliance does not support Internet Explorer if the Compatibility View is turned on. Ensure that the Compatibility View in Internet Explorer is turned off. The Compatibility View option is under the Tools menu in the Internet Explorer browser. Help page content does not display When you click the Help link from the appliance user interface in Microsoft Internet Explorer version 9.0 or later, the topic content might not display. Solution: Ensure that the Compatibility View in Internet Explorer is turned on. The Compatibility View option is under the Tools menu in the Internet Explorer browser. The Help System supports compatibility mode. WebSEAL sends client certificate by default The isamcfg tool can configure a WebSEAL or Web Reverse Proxy instance to use client certificate authentication to the run time. The run time can be configured to optionally accept client certificates. When configured in this mode, WebSEAL or the Web Reverse Proxy sends a client certificate regardless of whether a certificate label is specified in the configuration. Solution: If you require client certificate authentication, ensure that a valid client certificate is specified in the ssl-keyfile-label entry of the [rtss-cluser:<cluster name>] stanza. If you do not require client certificate authentication, either disable the optional acceptance of client certificates or specify an invalid client certificate label in the ssl-keyfile-label entry of the [rtss-cluser:<cluster name>] stanza. This method ensures that WebSEAL does not send a client certificate. 3

14 A junction error occurs when a duplicate dn or certificate label is detected The isamcfg tool imports the Access Manager server certificate to the WebSEAL or Web Reverse Proxy keystore when it uses an SSL connection. If an entry exists in this keystore with the same dn or the same certificate label, an error can occur when it creates the junction to the Access Manager server. Solution: You must manually export the certificate that is presented by the run time and import it to the WebSEAL key database as a signer certificate. The junction then becomes accessible. A cluster configuration update fails to deploy and generates a timeout error message An update to the cluster configuration, such as the External Reference Entity IP address or First Port value, might fail to deploy in the allotted time. The following error message is printed in the event log: WGASY0007E The pending changes failed to deploy within the allotted time. Solution: Increase the wga.cmd.timeout value. In the local management interface, select Manage System Settings > System Settings > Advanced Tuning Parameters. Add a parameter that is called wga.cmd.timeout and set the timeout value in seconds. The default value is 300 seconds. Access tokens are not cleared in a failed resource owner password credential flow The access tokens that are generated from resource owner password credential flow are not cleared when resource owner password validation fails. These tokens must be removed so that malicious users cannot use the resource owner password credential flow to fill up the token cache by using a public client. Solution: In the pre-mapping rule, make a validate request to the user directory with the user name and password that you want to verify. This method stops the resource owner password credential flow before it generates the access token if the user name and password verification fails. For more information, see OAuth mapping rule methods in the Configuration Guide. Policies with X.500 names If your LDAP root DN is secauthority=default, you can use the = (equal) operator only in policies that use X.500 names userdn and groupsdn. Database Maintenance panel returns a retrieval error The following error message returns in the Database Maintenance panel after the location of the runtime database is changed from Local to the cluster to Remote to the cluster in the Cluster Configuration panel: 4 IBM Single Sign On for Bluemix Version 2.0: Identity Bridge Troubleshooting topics

15 System Error FBTRBA091E The retrieval failed because the resource cannot be found. Solution: Complete the following steps to restart the local management interface: 1. Use an ssh session to access the local management interface. 2. Log in as the administrator. 3. Type lmi and press Enter. 4. Type restart and press Enter. 5. Type exit and press Enter. Error message is returned when IBM soliddb is used to deploy an external runtime database When you deploy an external runtime database with IBM soliddb, isam_mobile_soliddb.sql attempts to create a duplicate index on the RBA_USER_DEVICE table. The following error message is returned: SOLID Table Error 13199: Duplicate index definition Solution: Ignore this error message. Investigate any other error messages about the deployment of the run time database. Cannot export and import a template page file in the same session If you export a template page file and immediately try to import a file, no action occurs, and the file is not imported. Solution: After you export a file, refresh the browser before you try to import a file. Authentication alias message in startup log The following message might be displayed in the runtime server startup log: I J2CA8050I: An authentication alias should be used instead of defining a user name and password on com.ibm.ws.jdbc.datasource-config/properties-0 Solution: Ignore this message. Creating access control policies during switch between daylight saving time and standard time If you create an access control policy when the appliance clock switches from daylight saving time (DST) to standard time (ST), the policy might not work as you expect. For example: 1. Create an access control policy at 1:45 am on the Sunday when DST returns to ST. 2. Modify the policy at 2:15 am DST, which is 1:15 am ST and within 1 hour of the creating the policy. The policy that you created in step 1 is used because it is newer (more recently created) than the modified policy in step 2. Solution: To correct this issue, modify and republish the policy that you want to use after 1:45 am standard time. Chapter 2. Known issues and solutions 5

16 Filter stops working after changing a parameter on the Advanced Configuration panel You can filter the data displayed on the Advanced Configuration panel. After you change a parameter and click the Change button, the filter is no longer applied to the displayed data. Solution: Click Enter next to the filter field to reapply the filter. Reverse proxy user password page is inaccessible After authenticating with the authentication mechanisms, the reverse proxy user password change page (/pkmspasswd) becomes inaccessible. Solution:This page is working as designed. The reverse proxy makes this page inaccessible for users who are authenticated with the External Authentication Interface (EAI). The authentication service relies on EAI to establish the authenticated session. Database failover capabilities vary during a cluster upgrade The distributed session cache, runtime database, and configuration database have different failover capabilities during cluster upgrades. Table 1. Database Distributed session cache Runtime database Configuration database Behaviour If the primary master fails, failover goes to secondary master. Changes are done in the secondary master and reconciliation occurs when primary master is restored. If the primary master fails, there is no failover to the secondary master. No changes are possible on the primary or secondary master until the primary master is back online. Issue 1 When a high availability cluster is active, a situation exists during the firmware upgrade on the primary node where the configuration database is read-only. A read-only database prevents the upgrade process from writing to the configuration database when creating new tables, modifying schema of existing tables, and inserting or updating rows on tables. The reason the database on the primary node becomes read-only is the firmware upgrade requires the appliance to be rebooted. During a reboot, the high availability controller switches the secondary master to be read-write and act as the temporary primary master. When the primary node reboots and the database starts: 1. It recognizes that the secondary node is in control and starts in read-only mode. 2. The appliance cluster manager includes a background thread which will eventually switch the primary node to resume its role as the primary master database. 6 IBM Single Sign On for Bluemix Version 2.0: Identity Bridge Troubleshooting topics

17 3. The database on the primary node becomes writeable. However, during an upgrade, the database upgrade scripts are executed before the primary database has become writeable. Issue 2 For the distributed session cache and runtime database, a situation exists where changes to the secondary databases are not reflected in the primary database after the completion of a cluster upgrade. Solution: To address Issue 1, make the cluster a single master cluster for the duration of the firmware upgrade: 1. On the master node, use the Cluster Configuration panel to remove secondary settings and another high availability cluster member if applicable. Do not change the Primary setting. 2. Wait for the cluster to synchronize. 3. Upload and install the firmware.pkg on the primary node appliance. 4. Restart the appliance. 5. Upload and install the firmware.pkg to other cluster member appliances. 6. Reboot each cluster member appliance. 7. On the master node, use the Cluster Configuration panel to set high availability cluster members back to the original settings. Wait for the cluster to synchronize. The appliance firmwares have now been upgraded and the cluster is operational. To address Issue 2, stop traffic to the cluster before starting the upgrade. Error occurs after switching the runtime database in the appliance After you switch the runtime database from local to remote and deploying the pending changes, SQL-related runtime errors occur in the appliance. Solution: Restart the runtime. 1. In the local management interface, select Secure Bridge Settings > Runtime Parameters > Runtime Status. 2. Click Restart All Clustered Runtimes. Firmware version and Last update information not displayed in Update History and Overview section Firmware information is not displayed in the Update History section of the user interface. Information on Last update is not displayed in the Overview section of the user interface. This is the case for firmware upgrades and fixpacks. The firmware version can be determined using the Firmware Settings user interface on the appliance. To determine the firmware version: 1. Logon to the appliance as the administrator. 2. Click Manage System Settings > Firmware Settings. The active partition is reported. The Details column includes the firmware version. Chapter 2. Known issues and solutions 7

18 Alternatively, you can verify the firmware version from Manage System Settings > Updates and Licensing > Overview. Information on Last update not displaying is a known limitation. 8 IBM Single Sign On for Bluemix Version 2.0: Identity Bridge Troubleshooting topics

19 Chapter 3. Known limitations Consider these known limitations when you are configuring the environment. External clients cannot use the session cache The distributed session cache in the appliance does not support external clients. The Support internal and external clients option on the Session Cache tab on the Cluster Configuration management page is not relevant in the identity bridge environment. The appliance disregards the Port, Keyfile, and Label fields, which relate to external clients. Local management interface (LMI) session timeouts LMI sessions expire after the duration of time that is specified by the Session Timeout field on the Administrator Settings page. When a session timeout occurs, you are automatically logged out and any unsaved data on the current page is lost. Save your configuration updates in the LMI regularly to avoid data loss in the event of a session timeout. Certain characters in JSON messages are displayed in Unicode Non-ASCII characters are escaped in the JSON response from the REST API endpoints. This format is specified in RFC The non-ascii character is represented as a six-character sequence: a reverse solidus, followed by the lowercase letter u, and followed by four hexadecimal digits that encode the code point of the character. For example, \u00e9. For more information, see RFC

20 10 IBM Single Sign On for Bluemix Version 2.0: Identity Bridge Troubleshooting topics

21 Chapter 4. Deploying pending changes Some configuration and administration changes require an extra deployment step. About this task When you use the graphical user interface on the appliance to specify changes, some configuration and administration tasks take effect immediately. Other tasks require a deployment step to take effect. For these tasks, the appliance gives you a choice of deploying immediately or deploying later. When you must make multiple changes, you can wait until all changes are complete, and then deploy all of them at one time. When a deployment step is required, the user interface presents a message that says that there is an undeployed change. The number of pending changes is displayed in the message, and increments for each change you make. Note: If any of the changes require the runtime server to be restarted, the restart occurs automatically when you select Deploy. The runtime server will then be unavailable for a period of time until the restart completes. Procedure 1. When you finish making configuration changes, select Click here to review the changes or apply them to the system. The Deploy Pending Changes window is displayed. 2. Select one of the following options: Option Cancel Description Do not deploy the changes now. Retain the undeployed configuration changes. The appliance user interface returns to the previous panel. Roll Back Abandon configuration changes. A message is displayed, stating that the pending changes were reverted. The appliance user interface returns to the previous panel. Deploy Deploy all configuration changes. When you select Deploy, a system message is displayed, stating that the changes were deployed. If any of the changes require the runtime server to be restarted, the restart occurs automatically when you select Deploy. The runtime server will then be unavailable for a period of time until the restart completes. 11

22 12 IBM Single Sign On for Bluemix Version 2.0: Identity Bridge Troubleshooting topics

23 Chapter 5. Support Information To isolate and resolve problems with your IBM products, you can use the troubleshooting and support information. This information contains instructions for using the problem-determination resources that are provided with your IBM products. Techniques for troubleshooting problems Troubleshooting is a systematic approach to solving a problem. The goal of troubleshooting is to determine why something does not work as expected and how to resolve the problem. Certain common techniques can help with the task of troubleshooting. The first step in the troubleshooting process is to describe the problem completely. Problem descriptions help you and the IBM technical-support representative know where to start to find the cause of the problem. This step includes asking yourself basic questions: v What are the symptoms of the problem? v Where does the problem occur? v When does the problem occur? v Under which conditions does the problem occur? v Can the problem be reproduced? The answers to these questions typically lead to a good description of the problem, which can then lead you to a problem resolution. What are the symptoms of the problem? When you start to describe a problem, the most obvious question is What is the problem? This question might seem straightforward; however, you can break it down into several more-focused questions that create a more descriptive picture of the problem. These questions can include: v Who, or what, is reporting the problem? v What are the error codes and messages? v How does the system fail? For example, is it a loop, hang, crash, performance degradation, or incorrect result? Where does the problem occur? Determining where the problem originates is not always easy, but it is one of the most important steps in resolving a problem. Many layers of technology can exist between the reporting and failing components. Networks, disks, and drivers are only a few of the components to consider when you are investigating problems. The following questions help you to focus on where the problem occurs to isolate the problem layer: v v Is the problem specific to one platform or operating system, or is it common across multiple platforms or operating systems? Is the current environment and configuration supported? 13

24 v v Do all users have the problem? (For multi-site installations.) Do all sites have the problem? If one layer reports the problem, the problem does not necessarily originate in that layer. Part of identifying where a problem originates is understanding the environment in which it exists. Take some time to completely describe the problem environment, including the operating system and version, all corresponding software and versions, and hardware information. Confirm that you are running within an environment that is a supported configuration; many problems can be traced back to incompatible levels of software that are not intended to run together or were not fully tested together. When does the problem occur? Develop a detailed timeline of events that led up to a failure, especially for those cases that are one-time occurrences. You can most easily develop a timeline by working backward: Start at the time an error was reported (as precisely as possible, even down to the millisecond), and work backward through the available logs and information. Typically, you need to look only as far as the first suspicious event that you find in a diagnostic log. To develop a detailed timeline of events, answer these questions: v Does the problem happen only at a certain time of day or night? v How often does the problem happen? v What sequence of events leads up to the time that the problem is reported? v Does the problem happen after an environment change, such as upgrading or installing software or hardware? Responding to these types of questions can give you a frame of reference in which to investigate the problem. Under which conditions does the problem occur? Knowing which systems and applications are running at the time that a problem occurs is an important part of troubleshooting. These questions about your environment can help you to identify the root cause of the problem: v Does the problem always occur when the same task is being completed? v Does a certain sequence of events need to happen for the problem to occur? v Do any other applications fail at the same time? Answering these types of questions can help you explain the environment in which the problem occurs and correlate any dependencies. Remember that just because multiple problems might occur around the same time, the problems are not necessarily related. Can the problem be reproduced? From a troubleshooting standpoint, the ideal problem is one that can be reproduced. Typically, when a problem can be reproduced you have a larger set of tools or procedures at your disposal to help you investigate. Problems that you can reproduce are often easier to debug and solve. However, problems that you can reproduce can have a disadvantage: If the problem is of significant business affect, you do not want it to recur. If possible, 14 IBM Single Sign On for Bluemix Version 2.0: Identity Bridge Troubleshooting topics

25 Searching knowledge bases Getting fixes re-create the problem in a test or development environment, which typically offers you more flexibility and control during your investigation. v Can the problem be re-created on a test system? v Are multiple users or applications that encounter the same type of problem? v Can the problem be re-created by running a single command, a set of commands, or a particular application? You can often find solutions to problems by searching IBM knowledge bases. You can optimize your results by using available resources, support tools, and search methods. About this task You can find useful information by searching the information center for this product. However, sometimes you need to look beyond the information center to answer your questions or resolve problems. Procedure To search knowledge bases for information that you need, use one or more of the following approaches: v Search for content by using the IBM Support Assistant (ISA). ISA is a no-charge software serviceability workbench that helps you answer questions and resolve problems with IBM software products. You can find instructions for downloading and installing ISA on the ISA website. v Find the content that you need by using the IBM Support Portal. The IBM Support Portal is a unified, centralized view of all technical support tools and information for all IBM systems, software, and services. The IBM Support Portal lets you access the IBM electronic support portfolio from one place. You can tailor the pages to focus on the information and resources that you need for problem prevention and faster problem resolution. Familiarize yourself with the IBM Support Portal by viewing the demo videos ( about this tool. These videos introduce you to the IBM Support Portal, explore troubleshooting and other resources, and demonstrate how you can tailor the page by moving, adding, and deleting portlets. v v Search for content by using the IBM masthead search. You can use the IBM masthead search by typing your search string into the Search field at the top of any ibm.com page. Search for content by using any external search engine, such as Google, Yahoo, or Bing. If you use an external search engine, your results are more likely to include information that is outside the ibm.com domain. However, sometimes you can find useful problem-solving information about IBM products in newsgroups, forums, and blogs that are not on ibm.com. Tip: Include IBM and the name of the product in your search if you are looking for information about an IBM product. A product fix might be available to resolve your problem. Chapter 5. Support Information 15

26 About this task Procedure To find and install fixes: 1. Obtain the tools required to get the fix. 2. Determine which fix you need. 3. Download the fix. Open the download document and follow the link in the Download package section. 4. Apply the fix. Follow the instructions in the Installation Instructions section of the download document. 5. Subscribe to receive weekly notifications about fixes and other IBM Support information. Getting fixes from Fix Central You can use Fix Central to find the fixes for IBM products. With Fix Central, you can search, select, order, and download fixes for your system with a choice of delivery options. A product fix might be available to resolve your problem. Procedure Contacting IBM Support To find and install fixes: 1. Obtain the tools that are required to get the fix. If it is not installed, obtain your product update installer. You can download the installer from Fix Central. This site provides download, installation, and configuration instructions for the update installer. 2. Select the product, and select one or more check box that are relevant to the problem that you want to resolve. 3. Identify and select the fix that is required. 4. Download the fix. a. Open the download document and follow the link in the Download Package section. b. When downloading the file, ensure that the name of the maintenance file is not changed. This change might be intentional, or it might be an inadvertent change that is caused by certain web browsers or download utilities. 5. Apply the fix. a. Follow the instructions in the Installation Instructions section of the download document. b. For more information, see the Installing fixes with the Update Installer topic in the product documentation. 6. Optional: Subscribe to receive weekly notifications about fixes and other IBM Support updates. IBM Support assists with product defects, answers FAQs, and helps users resolve problems with the product. 16 IBM Single Sign On for Bluemix Version 2.0: Identity Bridge Troubleshooting topics

27 Before you begin After you try to find your answer or solution by using other self-help options such as technotes, you can contact IBM Support. Before you contact IBM Support, your company or organization must have an active IBM software subscription and support contract, and you must be authorized to submit problems to IBM. For information about the types of available support, see the Support portfolio topic in the Software Support Handbook. Procedure To contact IBM Support about a problem: 1. Define the problem, gather background information, and determine the severity of the problem. For more information, see the Getting IBM support topic in the Software Support Handbook. 2. Gather diagnostic information. 3. Submit the problem to IBM Support in one of the following ways: v Using IBM Support Assistant (ISA): v Online through the IBM Support Portal: You can open, update, and view all of your service requests from the Service Request portlet on the Service Request page. v By telephone for critical, system down, or severity 1 issues: For the phone number to call in your region, see the Directory of worldwide contacts web page. Results If the problem that you submit is for a software defect or for missing or inaccurate documentation, IBM Support creates an Authorized Program Analysis Report (APAR). The APAR describes the problem in detail. Whenever possible, IBM Support provides a workaround that you can implement until the APAR is resolved and a fix is delivered. IBM publishes resolved APARs on the IBM Support website daily, so that other users who experience the same problem can benefit from the same resolution. What to do next Exchanging information with IBM To diagnose or identify a problem, you might need to provide IBM Support with data and information from your system. In other cases, IBM Support might provide you with tools or utilities to use for problem determination. Sending information to IBM Support To reduce the time that is required to resolve your problem, you can send trace and diagnostic information to IBM Support. Procedure To submit diagnostic information to IBM Support: 1. Open a problem management record (PMR). Chapter 5. Support Information 17

28 2. Collect the diagnostic data that you need. Diagnostic data helps reduce the time that it takes to resolve your PMR. You can collect the diagnostic data manually or automatically: v Collect the data manually. v Collect the data automatically. 3. Compress the files by using the.zip or.tar file format. 4. Transfer the files to IBM. You can use one of the following methods to transfer the files to IBM: v IBM Support Assistant v The Service Request tool v Standard data upload methods: FTP, HTTP v Secure data upload methods: FTPS, SFTP, HTTPS v All of these data exchange methods are explained on the IBM Support website. Receiving information from IBM Support Occasionally an IBM technical-support representative might ask you to download diagnostic tools or other files. You can use FTP to download these files. Before you begin Ensure that your IBM technical-support representative provided you with the preferred server to use for downloading the files and the exact directory and file names to access. Procedure To download files from IBM Support: 1. Use FTP to connect to the site that your IBM technical-support representative provided and log in as anonymous. Use your address as the password. 2. Change to the appropriate directory: a. Change to the /fromibm directory. cd fromibm b. Change to the directory that your IBM technical-support representative provided. cd nameofdirectory 3. Enable binary mode for your session. binary 4. Use the get command to download the file that your IBM technical-support representative specified. get filename.extension 5. End your FTP session. quit Subscribing to Support updates To stay informed of important information about the IBM products that you use, you can subscribe to updates. 18 IBM Single Sign On for Bluemix Version 2.0: Identity Bridge Troubleshooting topics

29 About this task By subscribing to receive updates about this product, you can receive important technical information and updates for specific IBM Support tools and resources. You can subscribe to updates by using one of two approaches: RSS feeds and social media subscriptions For general information about RSS, including steps for getting started and a list of RSS-enabled IBM web pages, visit the IBM Software Support RSS feeds site. My Notifications With My Notifications, you can subscribe to Support updates for any IBM product. (My Notifications replaces My Support, which is a similar tool that you might have used in the past.) With My Notifications, you can specify that you want to receive daily or weekly announcements. You can specify what type of information you want to receive (such as publications, hints, and tips, product flashes (also known as alerts), downloads, and drivers). My Notifications enable you to customize and categorize the products about which you want to be informed and the delivery methods that best suit your needs. Procedure To subscribe to Support updates: 1. Subscribe to the RSS feeds by accessing the IBM Software Support RSS feeds site and subscribe to the product feed. 2. Subscribe to My Notifications by going to the IBM Support Portal and click My Notifications in the Notifications portlet. 3. Sign in using your IBM ID and password, and click Submit. 4. Identify what and how you want to receive updates. a. Click the Subscribe tab. b. Select the appropriate software brand or type of hardware. c. Select one or more products by name and click Continue. d. Select your preferences for how to receive updates, whether by , online in a designated folder, or as an RSS or Atom feed. e. Select the types of documentation updates that you want to receive, for example, new information about product downloads and discussion group comments. f. Click Submit. Results Until you modify your RSS feeds and My Notifications preferences, you receive notifications of updates that you requested. You can modify your preferences when needed (for example, if you stop using one product and begin using another product). Related information IBM Software Support RSS feeds Subscribe to My Notifications support content updates My Notifications for IBM technical support Chapter 5. Support Information 19

30 My Notifications for IBM technical support overview 20 IBM Single Sign On for Bluemix Version 2.0: Identity Bridge Troubleshooting topics

31 Index B browser known issues 3 C cluster update known issue 3 Compatibility View Help System solution 3 known issues 3 D database deletions known issue 3 deploying changes 11 distributed session cache 9 E external clients limitation 9 F Fix Central, get fixes 16 format message ID 1 messages 1 H Help System known issue 3 I IBM Message Standard 1 ID format, messages 1 Internet Explorer Compatibility View known issue 3 Help System known issue 3 isamcfg SSL keyfile 3 SSL keyfile stash 3 WebSEAL configuration file 3 Microsoft Internet Explorer Compatibility View known issue 3 Help System known issue 3 P pending changes 11 problem determination exchange information with IBM Support 17 overview 1 S serviceability improvements messages 1 Support internal and external clients option 9 support, contact IBM Support 17 supports internal clients only 9 T troubleshoot identifying problems, techniques for 13 overview 1 support Fix Central 16 fixes 16 IBM Support, send information 17 search knowledge bases 15 subscribe to Support updates 19 troubleshoot techniques 13 W wga.cmd.timeout tuning parameter 3 WGASY0007E error 3 M messages ID format 1 message standard 1 overview 1 serviceability improvements 1 standard format 1 21

32 22 IBM Single Sign On for Bluemix Version 2.0: Identity Bridge Troubleshooting topics

33

34 Printed in USA