Table of Contents

Search

  1. About the Security Guide
  2. Introduction to Informatica Security
  3. User Authentication
  4. LDAP Authentication
  5. Kerberos Authentication
  6. SAML Authentication for Informatica Web Applications
  7. Domain Security
  8. Security Management in Informatica Administrator
  9. Users and Groups
  10. Privileges and Roles
  11. Permissions
  12. Audit Reports
  13. Command Line Privileges and Permissions
  14. Custom Roles
  15. Default List of Cipher Suites

SAML Authentication Overview

SAML Authentication Overview

You can configure Security Assertion Markup Language (SAML) authentication for Informatica web applications.
Security Assertion Markup Language is an XML-based data format for exchanging authentication information between a service provider and an identity provider. In an Informatica domain, the Informatica web application is the service provider.
You can configure the following Informatica web applications to use SAML authentication:
  • Informatica Administrator
  • Informatica Analyst
  • Metadata Manager
  • Enterprise Data Catalog
  • Enterprise Data Preparation
Informatica supports the following identity providers:
  • Microsoft Active Directory Federation Services (AD FS)
  • PingFederate
For information about supported versions of these identity providers, see the Product Availability Matrix on Informatica Network: https://network.informatica.com/community/informatica-network/product-availability-matrices.
SAML authentication cannot be used in an Informatica domain configured to use Kerberos authentication.
If you enable a domain to use SAML authentication, all web applications that run in the domain use the identity provider you configure in the domain by default. However, you can configure web applications that run in a domain to use different identity providers. For example, you might configure Informatica Administrator to use AD FS as the identity provider, and configure Informatica Analyst to use PingFederate as the identity provider.
For more information about configuring web applications to use different identity providers, see Configuring Web Applications to Use Different Identity Providers.


Updated June 26, 2020