Table of Contents


  1. Abstract
  2. Installation and Upgrade
  3. 10.2 HF1 Fixed Limitations and Closed Enhancements
  4. 10.2 HF1 Known Limitations
  5. 10.2 Fixed Limitations and Closed Enhancements
  6. 10.2 Known Limitations
  7. Emergency Bug Fixes Merged into 10.2
  8. Informatica Global Customer Support

Security Fixed Limitations (10.2)

Security Fixed Limitations (10.2)

Review the Release Notes of previous releases for information about previous fixed limitations.
The following table describes fixed limitations:
When you synchronize an LDAP security domain with an LDAP directory server, references to LDAP user accounts that belong to groups in the native security domain are not deleted. As a result, you cannot perform operations on the native security domain groups containing the references.
When you access a domain through an F5 Networks BIG-IP proxy server, you must log in to both the Administrator tool and the Monitoring tool.
LDAP users are not correctly associated with groups in an LDAP security domain if the distinguished name (DN) value for a user is not identical to the DN specified for the uniquemember attribute.
You cannot manage permissions for an LDAP group in Microsoft Active Directory if you change the group name from uppercase letters to lowercase letters.
When a user in a SAML-enabled domain logs out of one Informatica web application, the user should also be logged out of all other Informatica web applications running in the same browser session. However a user is not logged out of all web applications if the user's LDAP account name includes an ampersand (&) character.
The following table describes closed enhancement requests:
If you select Oracle Directory as the LDAP Type when you use the Administrator tool or infacmd to import users into an LDAP security domain, the user email address is set as the username attribute.

Updated June 29, 2020