Tivoli Federated Identity Manager 6.2.0 Fixpack 9 (6.2.0-TIV-TFIM-FP0009)
This is a cumulative Fix Pack (FP) patch for a variety of problems in the
components that compose the TFIM 6.2.0 product. It upgrades a TFIM 6.2.0
installation to TFIM 220.127.116.11.
This fix pack corrects problems in IBM Tivoli Federated Identity Manager (Federated Identity Manager), Version 6.2.0. It requires that the IBM Federated Identity Manager, Version 6.2.0, be installed. After installing this fix pack, your Federated Identity Manager installation will be at version 18.104.22.168.
Potential cross-site scripting vulnerabiltity via macros in event page template files
Some IBM Tivoli Federated Identity Manager page macros might be vulnerable to cross site scripting attacks when their values are not properly encoded. Contact IBM Support for the list of macros that might be subjected to this issue. To remediate this, add the macros provided by IBM Support to the list of comma-separated tokens in the runtime custom property SPS.PageFactory.HtmlEscapedTokens. Add these macro so that their values are HTML-escaped in the template files. For example, if the list of macros provided is:
the value of the runtime custom property SPS.PageFactory.HtmlEscapedTokens with the above macros added can be:
NOTE: Other macros that are prone to cross site scripting vulnerability can also be added to SPS.PageFactory.HtmlEscapedTokens. The value of this runtime custom property will be revised periodically and update as needed. For more information regarding the runtime custom property, access http://pic.dhe.ibm.com/infocenter/tivihelp/v2r1/index.jsp?topic=%2Fcom.ibm.tivoli.fim.doc_6.2.0%2Freference%2FCustomPropsSPS.html.
Possible security exposure with IBM WebSphere Application Server with WS-Security enabled applications using LTPA tokens (CVE-2011-1377)
The security that the IBM WebSphere Application Server provides might be weaker than expected when using web services security (WS-Security). A user might randomly gain elevated privileges on the provider system. WS-Security might assign the identity of a previously processed LTPA token to a new inbound LTPA token after authentication. This impacts applications using either JAX-WS and JAX-RPC.
The same fix applies to the IBM WebSphere Application Server Standalone, Network Deployment and Embedded (eWAS) versions. It also applies to the eWAS version that is included with IBM Tivoli Federated Identity Manager. For more information regarding the vulnerability and the fix, access http://www.ibm.com/support/docview.wss?uid=swg21587536
Use the IBM WebSphere Update Installer (WUI) to apply the fix. If the WUI has not been previously installed, the WUI can be downloaded from http://www.ibm.com/support/docview.wss?rs=180&uid=swg24020448. For detailed instructions on how to install the IBM WebSphere Update Installer, see the WebSphere Update Installer documentation.
Apply the fix provided here to all Tivoli Federated Identity Manager environments that use the affected versions of IBM WebSphere Application Server as soon as possible. Select the fix that applies to your IBM WebSphere Application Server environment and reference the corresponding readme file for detailed fix installation instructions.
Denial of Service Security Exposure with Java JRE/JDK hanging when converting 2.2250738585072012e-308 number (CVE-2010-4476)
This security alert addresses a serious security issue: CVE-2010-4476 (Java Runtime Environment hangs when converting "2.2250738585072012e-308" to a binary floating-point number). This vulnerability might cause the Java Runtime Environment to hang, go into an infinite loop, and/or crash resulting in a denial of service exposure. The JRE might hang if the number is written without scientific notation (324 decimal places). In addition to the Application Server being exposed to this attack, any Java program using the Double.parseDouble method is also at risk of this exposure including any customer written application or third party written application.
The following products contain affected versions of the Java Runtime Environment:
The same iFix applies to the IBM WebSphere Application Server Standalone, Network Deployment and Embedded (eWAS) versions. It also applies to the eWAS version that is included with IBM Tivoli Federated Identity Manager. For more information regarding the vulnerability and the iFix access, see http://www-01.ibm.com/support/docview.wss?uid=swg21462019
The IBM WebSphere Update Installer (WUI) must be used to apply the fix. If the WUI has not previously installed, download the WUI from http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg24020448. For detailed instructions on how to install the IBM WebSphere Update Installer access here.
Apply the fix provided here to all Tivoli Federated Identity Manager environments that use the affected versions of IBM WebSphere Application Server as soon as possible. Select the fix that applies to your IBM WebSphere Application Server environment and reference the corresponding readme file for detailed iFix installation instructions.
JAVA.LANG.RUNTIMEEXCEPTION: SRV.8.2: REQUESTWRAPPER OBJECTS MUST EXTEND SERVLETREQUESTWRAPPER OR HTTPSERVLETREQUESTWRAPPER (PM10357)
This APAR PM10357 is reported for WebSphere Application Server (WAS) v6.1. As a result of this APAR, operations in the IBM Tivoli Federated Identity Manager Management Console can fail with the following exception observed in the log if the Management Console is deployed on an affected version of WAS v6.1:
java.lang.RuntimeException: SRV.8.2: RequestWrapper objects must extend ServletRequestWrapper or HttpServletRequestWrapper
Examples of operations that can fail include:
Apply the fix provided here to all Tivoli Federated Identity Manager environments that use the affected versions of IBM WebSphere Application Server. Select the fix that applies to your IBM WebSphere Application Server environment and reference the corresponding readme file for detailed iFix installation instructions.
The same fix applies to the IBM WebSphere Application Server Standalone, Network Deployment and Embedded (eWAS) versions. It also applies to the eWAS version that is included with IBM Tivoli Federated Identity Manager.
The IBM WebSphere Update Installer (WUI) must be used to apply the fix. If the WUI has not previously installed, download the WUI from http://www-01.ibm.com/support/docview.wss?rs=180&uid=swg24020448. For detailed instructions on how to install the IBM WebSphere Update Installer access here.
Fix pack contents and distribution
This fix pack package contains:
This fix pack is distributed as an electronic download from the IBM Support Web Site.
This fix pack package supports the same operating system releases that are listed in the Hardware and software requirements topic for Federated Identity Manager Version 6.2.0.
ATTENTION: In April 2009, FP0002 added support for WebSphere Application Server Release 7.0 Fix Pack 3 (release date March 27, 2009)
ATTENTION: In May 2009, FP0002 added support for Windows 2003 Server x86-64.
ATTENTION: In July 2009, FP0002 added support for Oracle 10g.
ATTENTION: In September 2009, FP0002 added support for Suse Linux Enterprise Server 11 (SLES 11) x86, x86-64, zSeries, pSeries. Note: Defect 91189, Webseal not configuring on SLES 11
ATTENTION: In November 2009, FP0003 added support for Internet Explorer 8 (IE8
ATTENTION: In November 2009, FP0003 added support for Windows 2008 R2 Server (x86-64). Note: 90900: GUI not thrown on GUI install for WIN2K8 R2, Workaround: -console mode is required on Windows 2008 R2 (e.g., on linux ./install_linux_x86.bin -console)
ATTENTION: In December 2009, FP0003 added support for Mozilla FireFox 3.5.
ATTENTION: In March 2010, FP0002 added support for z/OS 1.11 System z.
ATTENTION: In December 2010, FP0008 added support for Red Hat Enterprise Linux (RHEL) 5.0 Advanced Platform x86, Red Hat Enterprise Linux (RHEL) 5.0 Advanced Platform x86-64, SUSE Linux Enterprise Server (SLES) 10.0 x86, SUSE Linux Enterprise Server (SLES) 10.0 x86-64, SUSE Linux Enterprise Server (SLES) 11.0 x86, SUSE Linux Enterprise Server (SLES) 11.0 x86-64, Windows Server 2008 Enterprise Edition x86, Windows Server 2008 Enterprise Edition x86-64, Windows Server 2008 Standard Edition x86, Windows Server 2008 Standard Edition x86-64 and Windows Server 2008 R2 Enterprise Edition x86-64 on VMware ESX 4.0.
ATTENTION: In December 2010, FP0008 added support for Red Hat Enterprise Linux (RHEL) 5.0 Advanced Platform x86, Red Hat Enterprise Linux (RHEL) 5.0 Advanced Platform x86-64, SUSE Linux Enterprise Server (SLES) 10.0 x86, SUSE Linux Enterprise Server (SLES) 10.0 x86-64, SUSE Linux Enterprise Server (SLES) 11.0 x86, SUSE Linux Enterprise Server (SLES) 11.0 x86-64, Windows Server 2008 Enterprise Edition x86, Windows Server 2008 Enterprise Edition x86-64, Windows Server 2008 Standard Edition x86, Windows Server 2008 Standard Edition x86-64 and Windows Server 2008 R2 Enterprise Edition x86-64 on Red Hat Enterprise Virtualization Hypervisor (RHEV-H) / KVM 5.4.
ATTENTION: In December 2010, FP0008 added support for AIX 6.1 on IBM Power7 PowerVM Hypervisor. Support for POWER 7 is dependent on the upgrade to ITDS 6.1 Fixpack 5.
ATTENTION: In December 2010, FP0008 added support for Red Hat Enterprise Linux (RHEL) 4.0 AS/ES System z, Red Hat Enterprise Linux (RHEL) 5.0 Advanced Platform System z, SUSE Linux Enterprise Server (SLES) 10.0 System z, SUSE Linux Enterprise Server (SLES) 11.0 System z, z/OS 1.10 and z/OS 1.11 on IBM z/VM Hypervisor 6.1.
ATTENTION: In December 2010, FP0008 added support for Red Hat Enterprise Linux (RHEL) 4.0 AS/ES System z, Red Hat Enterprise Linux (RHEL) 5.0 Advanced Platform System z, SUSE Linux Enterprise Server (SLES) 10.0 System z, SUSE Linux Enterprise Server (SLES) 11.0 System z, z/OS 1.10 and z/OS 1.11 on IBM PR/SM z10.
ATTENTION: In December 2010, FP0008 added support for IBM Tivoli Directory Server 6.2.
ATTENTION: In December 2010, FP0008 added support for Oracle Database 11g Enterprise Edition Release 1.
ATTENTION: In December 2010, FP0008 added support for Oracle Database 11g Enterprise Edition Release 2.
ATTENTION: In March 2011, FP0008 added support for LPAR AIX 7.1. Note: WPAR is not supported for any supported version of AIX.
Fix packs superseded by this fix pack
Federated Identity Manager consists of the following components that can be installed separately:
This fix pack applies only to the administration console, management service and runtime component, and Web services security management (first three components listed above). These three components must be at the same level. For example, if you install a fix pack for the management service and runtime component, you must install the corresponding fix packs for the administration console and WSSM components. If all three components are not at the same fix pack level, they are not guaranteed to interoperate with each other as designed.
APARs and defects fixed
Problems fixed by fix pack 6.2.0-TIV-TFIM-FP0009
The following problems are corrected by this fix pack. For more information about the APARs listed here, refer to the Tivoli Federated Identity Manager support site.
SYMPTOM: ClassCastException is thrown when adding a SAML 2.0 Identity Provider as a partner. This problem happens when the metadata of the Identity Provider contains SAML attributes.
SYMPTOM: LTPA Token Module is not calculating the expiration date correctly. When a token is renewed, the expiration date is added to the userdata structure expiration array. The new expiration date is the last item added to the array. The IBM Tivoli Federated Identity Manager was incorrectly taking the first item on the array.
SYMPTOM: ClassCastException is thrown when configuring LDAP alias service using the IBM Tivoli Federated Identity Manager Command Line. This problem happens if at least one LDAP server exists in the system.
SYMPTOM: THE WEBSPHERE APPLICATION SERVER POC CREATE WAS SECURITY CONTEXT WITH INSUFFICIENT UNIQUE ID.
SYMPTOM: In some SAML error circumstances, the IBM Tivoli Federated Identity Manager would return a NullPointerException when attempting to display an error page or return a SAML error to an artifact retrieval request.
SYMPTOM: Empty-valued attributes in an STSUniversalUser XML document are not preserved by the Java implementation when converting from XML to Java and back to XML.
SYMPTOM: The value of the attribute "IsDefault" of all assertion consumer services of the SAML 2.0 Service Provider partner is changed to "true" after clicking the button "OK" or "Apply" in the Partner Properties page in the IBM Tivoli Federated Identity Manager Console.
SYMPTOM: SAML 2.0 STS Module fails to validate the subject confirmation method correctly when the assertion is received as part of the SAML 2.0 Single Sign On operation. The specification requires that an assertion that is generated as part of a Single Sign On flow should at least include one of the subject confirmation methods of value urn:oasis:names:tc:SAML:2.0:cm:bearer.
SYMPTOM: SAML 2.0 SPS Module is setting the Destination attribute on LogoutReponse message when the request is received through SOAP binding at the Identity Provider and there is more than one service provider session that was authenticated based on the Identity Provider session. The Destination field might have the url for the incorrect partner that is not the one that send the LogoutRequest.
SYMPTOM: The IBM Tivoli Federated Identity Manager LTPA STS module support code is not thread safe. The code uses an static instance of a JDK class that is not thread safe causing undetermined results while verifying or generating the ltpa token signature on environments with high volume of transaction.
SYMPTOM: KERBEROS STS MODULE TO ENFORCE TOKEN ONE TIME USE.
SYMPTOM: Security update for the IBM Tivoli Federated Identity Manager Management Console.
SYMPTOM: ClassCastException is thrown when adding and modifying LDAP host using the IBM Tivoli Federated Identity Manager Command Line. This problem happens if the parameter "hostPort" is not 389, or the parameter "minConnections" is not 2, or the parameter "maxConnections" is not 10.
SYMPTOM: The SAML specification allows for the Identity Provider not to include an issuer value on the SAMLResponse as long as the assertion includes the value. The IBM Tivoli Federated Identity Manager SAML module was expecting for the issuer on the SAML Response to always be included. Such expectation was causing a Null Pointer Exception when the values was not included.
SYMPTOM: Opening a Tivoli Federated Identity Manager page or portlet from the WebSphere Application Server ISC causes a JNDI exception of the type NameNotFoundException to be logged in the WAS server log.
SYMPTOM: The IBM Tivoli Federated Identity Manager generates a NullPointerException when the SAMLResponse received from the Identity Provider does not include a Issuer value though the Issuer value is included in the assertion.
SYMPTOM: Duplicate STS chain mappings are created when adding a SAML 2.0 Service Provider as a partner. This problem happens if the metadata of the Service Provider contains at least three distinct assertion consumer services with at least three distinct URLs.
SYMPTOM: Ability for IVCRED STS Module to return error (default) or map to special user account for unauthenticated user token.
SYMPTOM: The SAML 2.0 SPS module during a Single Logout operation on Service Provider side is invoking the alias service regardless if email name id format was used to single sign on the user. While the Single Logout Operation is successful, an error is included on the logs though the alias operation is not required.
SYMPTOM: Mapping from single logout URL to protocol is deleted from the configuration file after clicking the button "OK" or "Apply" in the Federation Properties page in TFIM Console. This problem happens if the single logout bindings that are enabled are only HTTP-Redirect and SOAP. The missing mapping causes single logout operation to fail.
SYMPTOM: CommandException is thrown when exporting a key from a keystore using IBM Tivoli Federated Identity Manager Command Line. This problem happens if the parameter "exportPrivateKey" is specified with no value or with value "true".
SYMPTOM: ChainableRuntimeException is thrown when exporting a key from a keystore using the IBM Tivoli Federated Identity Manager Console. This problem happens if the IBM Tivoli Federated Identity Manager is deployed in certain WebSphere Application Server versions (e.g., WebSphere Application Server 7 Fix Pack 11).
SYMPTOM: Security update for the IBM Tivoli Federated Identity Manager Management Console.
SYMPTOM: Security update for the IBM Tivoli Federated Identity Manager Runtime.
Problems fixed by fix pack 6.2.0-TIV-TFIM-FP0008
SYMPTOM: Some of the IBM Tivoli Federated Identity Manager Console portlet pages cannot be displayed when it is installed in WebSphere Application Server 7 FP 11.
SYMPTOM: For a WS-Trust v1.3 request, FIM Security Token Service returns a response with multiple status codes, some of which contain WS-Trust v1.2 URI values.
SYMPTOM: IBM Tivoli Federated Identity Manager CLI Commands are not registered properly on WebSphere Application Server 7.0.
SYMPTOM: A valid WS-Trust 1.3 request fails if it includes an empty Issuer address value and the matching trust chain uses a wild card for Issuer value (e.g. with Issuer Address = *).
SYMPTOM: NullPointerException when creating a new STS chain that is not on Validate mode.
SYMPTOM: When reading the user header from WebSEAL or a generic point-of-contact, the username is URL decoded twice.
SYMPTOM: Exception occurs when using only.alias key selection criteria and the same key appears under multiple aliases.
SYMPTOM: The IBM Tivoli Federated Identity Manager artifact lookup routine can consume threads if the artifact received is not in the cache.
SYMPTOM: Using IBM Tivoli Federated Identity Manager ISC console makes it possible to remove a default mapping rule after the federation has been created.
SYMPTOM: The IBM Tivoli Federated Identity Manager SAML 2.0 SPS module throws a NullPointerException if an issuer value is not included on the SAML Response message.
SYMPTOM: When starting IBM Tivoli Federated Identity Manager the runtime nodes report exceptions while connecting to the config repository.
SYMPTOM: The fimivt application incorrectly relies on the provider id of the Service Provider to build the TARGET url for Single Sign On.
SYMPTOM: The IBM Tivoli Federated Identity Manager 6.2.0 will always sign the outgoing SAML response and SAML assertion when the HTTP/SOAP binding is used.
SYMPTOM: The IBM Tivoli Federated Identity Manager SAML 2.0 SPS Module does not create a session when the SAML AuthnRequest is received over the SOAP endpoint.
SYMPTOM: The ITFIM console metadata support fails to validate that mandatory endpoints are included. The SPSSODescriptor requires at least one AssertionConsumerService endpoint and the IDPSSODescriptor requires at least one SingleSignOnService url.
SYMPTOM: The ITFIM console partner properties page for a SAML 2.0 partner does not allow the user to modify the signature validation settings once set to typical or all signature settings.
SYMPTOM: The ITFIM Alias Service fails to provide enough information to differentiate between a fatal error reading aliases and the typical alias not found return.
SYMPTOM: ITFIM fails to send back a SOAP fault when a AuthnRequest with an invalid Issuer is received through the SOAP binding.
SYMPTOM: The Tivoli Federated Identity Manager SAML SSO Module should add appropriate information on the SAMLResponse message to allow exploiters to debug the reasons for artifact resolution failures.
SYMPTOM: STS service does not start when an illegal regular expression is provided for the "applies to", "issuer" or "token type" field of the STS chain mapping.
SYMPTOM: Unable to validate SAML2.0 tokens generated through WSSM.
SYMPTOM: LTPA XML security token issued by the STS has incorrect namespace.
SYMPTOM: TAM authorization module does not work with federation scenario. The TAM authorization module should be able to consume TAM credential bytes from the STSUU or from the current STS response object in the case where an IVCred module has run in issue mode prior to the TAM Authorization module.
SYMPTOM: Custom authorization tokens with attributes added by TAI are not processed by the IBM Tivoli Federated Identity Manager when creating a local token for TFIM with WebSphere point of contact.
SYMPTOM: Chinese language page templates that contain RPT / eRPT macro blocks and any text within those blocks contains DBCS characters, the RPT block is not filled in correctly when the IBM Tivoli Federated Identity Manager returns the page template.
SYMPTOM: If a service provider sends an SSO request containing the requested NameIDFormat of urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified the IDP implementation treats this as a persistent name identifier even if the DefaultNameIDFormat parameter for the partner or federation is set to a different name id format.
SYMPTOM: Migration fails for federations containing custom modules.
SYMPTOM: The LTPA token validate only looks on the current Element for a prefix definition.
SYMPTOM: The IBM Tivoli Federated Identity Manager Liberty SPS Module fails to serialize objects on the distribute cache.
SYMPTOM: The SAML 2.0 SPS module fails to apply the appropriate signature policy when the AuthnRequest is received using the artifact binding.
SYMPTOM: Wrong Target URL received at the Service Provider when doing an Identity Provider initiated Single Sign On using the Artifact Binding.
SYMPTOM: The identity provider behind a WebSphere point of contact throws an NullPointerException upon receiving an Single Logout Request request from service provider behind WebSEAL.
SYMPTOM: The IBM Tivoli Federated Identity Manager generated nonce value might have invalid characters in some situations.
SYMPTOM: The IBM Tivoli Federated Identity Manager SAML 2.0 SSO Module does not include enough error information on the response message to allow exploiters to debug the reasons for artifact resolution failures.
SYMPTOM: The ITFIM Authorization STS module connection pool deadlocks if connections are mark for removal.
SYMPTOM: Key alias not used to select key for XML signature and validation.
SYMPTOM: The ITFIM SAML 2.0 STS module is not honoring the default name id format parameter setting.
SYMPTOM: The ITFIM SAML 2.0 SPS module requires assertion signature even when the enclosing document is signed.
SYMPTOM: The SAML 2.0 SPS module signs the assertion in instances where the signature policy indicates that the assertion should not be signed.
SYMPTOM: The ITFIM SAML 2.0 STS module fails to validate a SAML 2.0 Assertion containing the NameID Format: urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified.
SYMPTOM: Recipient checking is not performed correctly by the SAML browser post support.
SYMPTOM: Invalid URL encoding of the RelayState parameter being performed by the SAML 2.0 SPS module.
SYMPTOM: The LTPA STS module sends an incorrect message when the token being validated is expired. The inserts on the message are on reverse order so the expiration date is displayed where the current date field should be.
SYMPTOM: Signed XML strings may be incorrectly encoded if the default file encoding for the operating system platform is not UTF-8 (e.g. Windows or AIX).
Problems fixed by fix pack 6.2.0-TIV-TFIM-FP0003
SYMPTOM: JDBC alias service is case sensitive for username.
SYMPTOM: The IBM Tivoli Federated Identity Manager IDP displays blank page when initiating solicited SSO for a second time.
SYMPTOM: The solution was to pass the relay state to the url so the customers can use the capability to override the target url using the credential attribute we already support.
SYMPTOM: When sending a Kerberos token to the Security Token Service the following error gets returned.
SYMPTOM: When upgrading an expired validation and encryption certificate that the keystore "view keys" shows the certificate as expired.
SYMPTOM: The Where Are You From (WAYF) Cookie lifetime needs to be configurable through the gui.
SYMPTOM: Passticket module incorrect logging verbosity.
SYMPTOM: When using samlsso and adding a target url with query string the parameters are lost and do not make it to the Service Provider.
SYMPTOM: SOAP faults are returned for WS-Trust validates request types.
SYMPTOM: When a runtime node is not configured a NullPointerException will be displayed in the browser when a sign-on transaction is attempted.
SYMPTOM: An incorrect ByteArrayOutputStream class was used that is not supported on all platforms.
SYMPTOM: The IBM Tivoli Federated Identity Manager fails to enforce signature policy properly for assertion.
SYMPTOM: When calling the artifact service and passing in an assertion to get back an artifact, if a custom module encounters an error and generates an exception stack trace that includes some special characters the Artifact service fails to include the exception on the SOAP Fault.
SYMPTOM: SAML 2.0 Configuration objects did not implement the Serializable interface.
SYMPTOM: The Management Console fixpack installation appears to complete successfully but the console doesn't operate correctly.
SYMPTOM: UPDATING THE PARTNER THROUGH PROPERTIES PAGE CORRUPTS THE CONFIG.
SYMPTOM: IBM Tivoli Federated Identity Manager fails to split url properly if "sps" is in the hostname.
SYMPTOM: After unlinking account, under some circumstances the Alias entry will not be removed.
SYMPTOM: IBM Tivoli Federated Identity Manager supported Oracle database for the TFIM alias service and that attempts to Use Oracle displayed errors.
SYMPTOM: Federation stops at wssoi screen.
SYMPTOM: Authorization decision query returning invalid decision query.
SYMPTOM: SAML 1.X module does not validate recipient value on response.
SYMPTOM: WS-TRUST 1.2 RequestSecurityTokenResponse message is different than the IBM Tivoli Federated Identity Manager 6.0.0 response message.
SYMPTOM: When THE IBM Tivoli Federated Identity Manager returns HTTP Cookies to the browser none of the secure bits are set.
SYMPTOM: ManageNameID defederate to an Service Provider where the alias does not exist.
SYMPTOM: SAML 2.0 IDP incorrectly process unspecified nameid format and always treats unspecified as a persistent id.
SYMPTOM: OpenID Caches are not per-federation.
SYMPTOM: OpenID relying-party association cache indexing error.
SYMPTOM: SOAP Client fails to initialize if using trust store with password.
SYMPTOM: HMAC-SHA256 ASSOC TYPE FAILS WITH NO-ENCRYPTION SESSION TYPE.
SYMPTOM: INCORRECT HANDLING OF LOST ASSOCIATION.
SYMPTOM: POST MESSAGE TO RETURN_TO URL SHOULD USE QUERY STRING IF POSSIBLE.
SYMPTOM: Form Post parameters should always be HTML encoded.
SYMPTOM: INTERNAL APAR FOR STS CONFORMANCE UPDATES.
SYMPTOM: INTERNAL APAR FOR TFIM 620 BUILD UPDATES.
SYMPTOM: INTERNAL APAR FOR TFIM 620 POINT OF CONTACT UPDATES.
SYMPTOM: Internal apar for SAML conformance updates.
SYMPTOM: The Event Handler extension point does not have access to event trail id.
SYMPTOM: tfimcfg tool doesn't work correctly in a multi-TAM domain.
SYMPTOM: SAML 2.0 Service Provider cannot validate SSL certificate on a list of trusted signers.
Problems fixed by fix pack 6.2.0-TIV-TFIM-FP0002
SYMPTOM: When triggering MNIDS operation, user does not have an alias stored in LDAP alias repository causes WebSEAL to return a server error.
SYMPTOM: A NullPointerException occurs when the SAML 2.0 Response does not contain an issuer.
SYMPTOM: The IBM Tivoli Federated Identity Manager complains "invalid_message_timestamp" when it receives an AuthnRequest with a SAML 2.0 IssueInstant with the date time format of "2008-07-01T13:30:50.830773Z"
SYMPTOM: STSMessageLogger does not work with multiple custom extensions. If two different chains utilize the STSMessageLogger, each with its own custom extension, only one of the extensions is used, and it is used by both chains.
SYMPTOM: STSMessageLogger does not work with Information Card IDP trust chain. When the STSMessageLogger is used as the first element in a trust chain for an Information Card IDP federation, and a card is used at a RP, the retrieval of a security token from the IDP fails. The IDP's WebSphere log shows the exception com.ibm.ws.webservices.engine.InternalException java.lang.IllegalArgumentException.
SYMPTOM: STSMessageLogger leaves open files locked on every IBM Tivoli Federated Identity Manager single-sign-on. When the STSMessageLogger is used in a trust chain for federated single sign-on, a new message logger file is created on every request. This rapidly results in file handle starvation.
SYMPTOM: When using the STSMessageLogger in a trust chain, a new file is created each time the "Reload Configurations" operation is performed (i.e. an OSGi runtime restart). These file handles are left open until WebSphere is restarted.
SYMPTOM: STSMessageLogger does not work when using WS-Trust 1.3 requests to the Tivoli Federated Identity Manager(TFIM) Security Token Service.
SYMPTOM: If an OP returns an OP-Identifier as the claimed identifier then the Relying-Party does not reject the login and allows authentication to succeed. The Replying-Party should reject the login. This issue affects only OpenID relying-party configurations during OP-identifier login.
SYMPTOM: OpenID Identity Provider hangs for long time when the relying-party sends an empty association handle. This results in a 30-second login time from this type of relying-party.
SYMPTOM: Some OpenID relying-party logins fail if an empty OpenID invalidate_handle value is sent in the login response. This problem is discovered when testing with WebSphere sMash.
SYMPTOM: If any page template that contains repeatable replacements is called with a replacement string that contains a single backslash or a dollar sign ($) then the replacement will not function correctly and will cause an IllegalArgumentException.
SYMPTOM: When tracing is turned on for the class com.tivoli.am.fim.infocard.delegates.InfoCardSTSDelegate and username/password information card is presented at the IDP to exchange for a SAML assertion, the user's password is exposed in clear text in trace.
SYMPTOM: OpenID Identity Provider SREG Namespace handling is broken. This problem is discovered when testing with WebSphere sMash. The OpenID identity provider should return the same SREG namespace as it received.
SYMPTOM: If a user trusts an OpenID relying party site, then deletes the trust from the site manager, and re-accesses the site, the consent-to-authenticate page is not being displayed when it should. This affects OpenID identity provider installations.
SYMPTOM: The OpenID 2.0 flows are non-conformant with the specification regarding a claimed identifier of identifier_select.
SYMPTOM: The closing macro delimiter, @OPTIONAL_ATTRIBUTE@, is missing from the consent.html template file for the label for optional SREG attributes. This only applies to OpenID identity provider federations.
SYMPTOM: OpenID RP in white-list scenario has severely slow performance.
SYMPTOM: The SAML Assertion token generator was not issuing Assertions correctly with SubjectConfirmation methods of holder-of-key and sender-vouches.
SYMPTOM: The publish plugins MBean action requires a domain to be passed in which causes a problem on systems where an IBM Tivoli Federated Identity Manager fix pack is applied before TFIM is configured.
SYMPTOM: Calls to IDMappingExtUtils.AddAliasForUser (which is typically made from a mapping rule) appear to succeed for non-existent users when they actually do not succeed. No alias is added. This problem is only applicable on systems with the IBM Tivoli Federated Identity Manager Alias service set to LDAP using TAM.
SYMPTOM: IDP source validation can not be done because the SAML 1.x browser-artifact doesn't contain the IDP source. Relying-parties must be able to check in the mapping rule that the Issuer contained in an assertion comes from the expected IDP partner. Without this capability rouge IDP's can spoof other IDP's assertion issuers.
SYMPTOM: When making STS requests to the WS-T 1.3 endpoint and authentication is enabled the requestor is not challenged to authenticate. This is because the WS-T 1.3 endpoint is missing the security constraint definition.
SYMPTOM: When uninstalling a fixpack, the process might fail at the very end. The UPDI log shows that the backup pak file for the fixpack could not be removed from the system. The problem affects only Windows platform.
SYMPTOM: The authentication data used during authentication callback is not made available when WebSeal is the PoC. The authentication mechanism being used for WebSeal PoC will not work because the authentication information such as the federation name, federation id, etc is not available.
SYMPTOM: When running the IBM Tivoli Federated Identity Manager using WebSphere Application Server as the Point of Contact at the Service Provider and WebSEAL at the IDP you will get a null pointer exception when logout is invoked from the Service Provider after successfully SSO.
SYMPTOM: The mapping rule example file ip_saml_20_email_nameid.xml is missing the namespace definition.
SYMPTOM: Routine build maintenance.
Problems fixed by fix pack 6.2.0-TIV-TFIM-FP0001
SYMPTOM: SAML 2.0 sessions expire immediately if the Amount of time the assertion is valid property is set to 4294080 seconds or greater (49.7 days or greater).
SYMPTOM: The WSSM trust client inserts erroneously a wsse namespace declaration into the wst:Base element when building requests to the trust service.
SYMPTOM: When running in a WebSphere 6.0.2.x environment, an error could occur when importing or upgrading a Federated Identity Manager 6.1.1.x domain, if custom token modules were developed for it.
SYMPTOM: A failure could occur while performing a SAML 2.0 single logout with the Service Provider, if the assistant name identifier was configured for the federation. The reported error was FBTSML219E.
SYMPTOM: The underlying secure protocol of an HTTPS connection created by Tivoli Federated Identity Manager is hard-coded to be SSL.
SYMPTOM: A timestamp is embedded within a passticket, but the time value interval is only granular to a full second.
SYMPTOM: An error could occur when attempting to run the tfimcfg tool in a Sun Solaris(TM) environment. The error was seen after the WebSEAL hostname was provided. The reported error stated that HTTPS is not a recognized protocol.
SYMPTOM: A performance degradation problem could occur when a federated single sign-on is attempted using LDAP registries containing millions of federated users. Depending on system and network conditions, a single sign-on operation could fail due to timeouts. The associated error reported a bad subtree search in LDAP.
SYMPTOM: A potential problem could occur with the use of the OpenId Provider local identifier. When using OpenID 2.0, the Relying Party should differentiate between Claimed Identifiers and OP-Local Identifiers. The Federated Identity Manager implementation used the OP-Local identifier, if present, for both values. This APAR fixes this problem by ensuring compliance with the OpenID 2.0 specification.
SYMPTOM: The OpenID Claimed Identifier was incorrectly normalized during HTML discovery. While performing an OpenID HTML discovery, the default action in the OpenID Relying Party was to follow redirections automatically which prevented the proper canonicalization of the final Claimed Identifier (claimed_id) URL.
SYMPTOM: LTPA v2 issued tokens that were rejected by WebSphere Application Server versions 6.0.2 and 6.1.
SYMPTOM: Logging and tracing could not be set for identity mapping from within an XSLT rule.
SYMPTOM: An XSLT identity mapping failure occurred when using the alias server with JDBC.
SYMPTOM: When an RST is sent to the STS with an empty textnode for either the AppliesTo, PortType or OperationName a null pointer exception is thrown.
SYMPTOM: The Higgins Client Jars directory adks/client/sts is missing some dependency JARs and includes unnecessary server JARs.
SYMPTOM: In an OpenID exchange the RP cannot display an appropriate login identifier on the screen to end users if the OP-identifier was used to login.
You must have the following software installed in order to install this fix pack:
- WebSphere Update Installer version 22.214.171.124 (see Update Installer below.)
- Enablement fix for Tivoli Federated Identity Manager (see Preinstallation enablement requirement for installing the fix pack for the first time)
Installation path specification for the Windows Server 2008 platform
This preinstallation item applies only to installations on a 64-bit Windows platform like Windows Server 2008.
Because Federated Identity Manager is a 32-bit application its default path when installing on Windows Server 2008 changes from
C:\Program Files (x86)\IBM\FIM
Note that this change to the installation path name also affects a 32-bit WebSphere Application Server on Windows Server 2008:
C:\Program Files (x86)\IBM\WebSphere
This fix pack requires the use of the WebSphere Update Installer version 126.96.36.199. Ensure that you have installed the correct version of the WebSphere Update Installer on each computer where you will install the fix pack. You can download the WebSphere Update Installer version 188.8.131.52 from the WebSphere Application Server Update Installer Web site. Installation instructions are on the download page.
Fix pack packaging
This Tivoli Federated Identity Manager 6.2.0-TIV-TFIM-FP0009 patch package is provided on the Tivoli Support Web site as a single downloadable zip file for each supported platform. After you select the package that is appropriate for the target platform, download the package and unzip the contents into a target directory, typically the default WebSphere Update Installer directory, either
for Windows or
You must unzip the downloaded file before you attempt to apply the patch. The unzipped contents are one or more pak files. Each pak file corresponds to one or more product components. For example, a fix pack might contain two pak files: one for the administration console and management service and runtime components, and one for the WSSM component. The full list of product components is described in Fix pack structure.
Use the WebSphere Update Installer to apply the fixes of each pak file to the target component on the system that you are updating. Apply all of the pak files that are required by your installation to ensure that the software levels in your environment are identical for all of the components for which a pak file is supplied. The fixes are tested against all affected components; therefore, to minimize any possible issue that can arise from applying a partial fix, ensure the you apply the complete set of files. See Installing the fix pack for specific instructions on using Update installer to apply the fixes.
Automatic creation of a backup directory
The Update Installer saves backup copies of the files that it replaces during the installation. You do not need to manually backup the Federated Identity Manager files.
Preinstallation enablement requirement for installing the fix pack for the first time
If this is the first time you are applying the fix pack to Federated Identity Manager, you must download and install the enablement fix for Tivoli Federated Identity Manager.
NOTE: Perform the following steps only if this is the first time you are applying a fix pack. You will not need to perform these steps for subsequent product updates.
1. Download the enablement fix into the Federated Identity Manager installation directory (typically C:\Program Files\IBM\FIM on a Windows system or /opt/IBM/FIM on a UNIX-based system) by clicking here.
2. Use the unzip option of the zip program for your operating system to unzip the file. On HP-UX, either use jar -xvf to unzip the file or download an unzip utility from the HPUX Connect site.
NOTE: If you are prompted to overwrite an existing file, accept it so that the target file is overwritten.
Installing the fix pack
NOTE: Before installing this fix pack, ensure that you have reviewed the prerequisites in Before installing the fix pack.
Downloading the fix pack
To obtain the fix pack:
1. Go to the IBM Tivoli Federated Identity Manager Support Web site.
2. Click Download. The fix pack (6.2.0-TIV-TFIM-FP0009) should be listed under Latest by date. If you do not see this fix pack listed, enter "6.2.0-TIV-TFIM-FP0009" in the Search field to access the link to the download window.
3. In the fix pack download window, scroll to the bottom of the window to view a listing of the download packages by platform.
4. Select the platform that corresponds to the target platform where you will apply the fixes. To ensure a secure download, you can select the DD (Download Director) option. If you have not used Download Director before, you will need to configure your browser to use Java security. Click What is DD? for configuration instructions.
Setting the WebSphere security passwords
If security is enabled on the WebSphere Application Server where Federated Identity Manager is installed, you must set the appropriate password values in the fim.appservers.properties file before you can apply the fix pack.
If security is not enabled, you can skip this step.
NOTE: If you add passwords to the fim.appservers.properties file, as described below, you specify these passwords using plain text. However, at the end of the fix pack installation process these passwords are obfuscated and will no longer be available in plain text format.
To specify security passwords, use the following procedure:
1. Using a text editor, open the file FIM_INSTALL_DIR/etc/fim.appservers.properties.
2. If the was.security.enabled property is present in the fim.appservers.properties file and is set to true then you must add two password properties to the file:
Applying the fix pack
1. Unzip the file you downloaded in Downloading the fix pack, preferably into the default WebSphere Update Installer's maintenence directory,
2. Ensure that the WebSphere Application Server that hosts the Federated Identity Manager runtime and management service component is running.
3. Ensure that the WebSphere Application Server that hosts the Federated Identity Manager console component is running.
4. Start the appropriate WebSphere Update Installer (typically located in C:\Program Files\IBM\WebSphere\UpdateInstaller on Windows systems, or in /opt/IBM/WebSphere/UpdateInstaller on UNIX-based systems).
5. In the Welcome window click Next. Federated Identity Manager will not be listed, but is supported.
6. Specify the path to the installation directory for Federated Identity Manager (typically C:\Program Files\IBM\FIM on Windows systems, or /opt/IBM/FIM on UNIX-based systems), then click Next.
7. Select Install maintenance in the dialog.
8. Specify the path where the fix pack (.pak) files were unzipped. The Update Installer automatically detects, enables, and displays the FIM fixes (pak files).
9. Determine which product components are installed on the system that you are updating. You should install only the pak files that correspond to the components on the target system. To determine the names and version levels of the product components installed on the target system, view the contents of the FIM_INSTALL_DIR/etc/version.propeties file with a text editor. The following list describes how to interpret the properties in the version.properties file:
Specifies that the management service and runtime component is installed at the level specified by version.
Specifies that the administration console component is installed at the level specified by version.
Specifies that the WS-provisioning runtime component is installed at the level specified by version.
Specifies that the Web services security management (WSSM) component is installed at the level specified by version.
Specifies that the Web plug-in (either the Internet information services (IIS) Web plug-in or the Apache/IBM HTTP Server Web plug-in) is installed at the level specified by version.
Apply the fix packs to the product's components in the following order:
1. Management service and runtime and administration console>
2. Other components
Note: If a domain is not created before application of the IBM Tivoli Federated Identity Manager fix pack, the fix pack installation completes successfully with a "Partially Successful" message.
10. Compare the list of installed components to the list of pak files in the WebSphere Update Installer and select the pak files that correspond to the installed components, then click Next.
Note: The WebSphere Update Installer allows you to select more than one pak file at a time for execution. Select only the pak files that correspond to the components that are installed on the system you are updating. If you accidentally install more pak files than are needed, you can separately uninstall any fix packs for components that are not installed on the target system.
11. If needed (for example, if you need to install multiple pak files on the target system, and you only installed one pak file), repeat the previous step to install any additional pak files on the target system.
Deploying the fix pack runtime component
After you install the fix pack, you need to redeploy the Tivoli Federated Identity Manager runtime. This task is identical to the deployment task you completed after the initial installation of the management service and runtime components. In a WebSphere cluster environment, you must ensure that the new runtime component is deployed to each WebSphere node.
The initial deployment steps are described in Creating and deploying a new domain in the Installation and Configuration Guide. The specific instructions for deploying the runtime begin in step 16.
Use the following procedure to deploy the updated Federated Identity Manager runtime:
1. Log in to the administration console.
2. Select Domain Management-> Runtime Node Management.
3. Ensure that the new runtime (version 184.108.40.206) is displayed as available, then click Deploy Runtime.
4. Wait for the deployment to finish by selecting Click to refresh runtime deployment status and check for completion...
5. If the domain was not created before application of the IBM Tivoli Federated Identity Manager fix pack, click Publish Plug-ins.
6. Verify that the currently deployed version is now 220.127.116.11 as follows:
1. Navigate to the Runtime Node Management window.
2. Look in the Runtime Management section of the Runtime Nodes portlet in the right panel and review the runtime information.
Current deployed version 18.104.22.168 [080922a]
Note: The number within the brackets [080922a] might be different from this example.
7. Repeat the previous step for each node in a WebSphere cluster environment.
|Download||RELEASE DATE||LANGUAGE||SIZE(Bytes)||Download Options
What is Fix Central(FC)?
|6.2.0-TIV-TFIM-FP0009-AIX||10 Aug 2011||English||106196944||FC|
|6.2.0-TIV-TFIM-FP0009-Linux||10 Aug 2011||English||106196944||FC|
|6.2.0-TIV-TFIM-FP0009-Solaris||10 Aug 2011||English||106196944||FC|
|6.2.0-TIV-TFIM-FP0009-Windows||10 Aug 2011||English||106196944||FC|
|6.2.0-TIV-TFIM-FP0009-ZOS||10 Aug 2011||English||106196944||FC|
|6.2.0-TIV-TFIM-FP0009-HPUX||10 Aug 2011||English||106196944||FC|
Problems (APARS) fixed
More support for:
Tivoli Federated Identity Manager
Software version: 6.2
Operating system(s): AIX, HP-UX, Linux, Solaris, Windows, z/OS
Reference #: 4029497
Modified date: 14 December 2012