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

Configuring Web Applications to Use Different Identity Providers

Configuring Web Applications to Use Different Identity Providers

You can configure Informatica 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.
When you enable a domain to use SAML authentication, all web applications that run in the domain use the default identity provider you specify when you enable SAML authentication in the domain. For example, if you configure AD FS as the identity provider, all web applications use AD FS as the identity provider, unless you configure a web application to use a different identity provider.
You specify the default identity provider when you use one of the following options to enable SAML authentication:
  • When you create the domain and install the Informatica services.
  • When you run the infasetup defineDomain command to create the domain.
  • When you run the infasetup updateDomainSamlConfig command to enable SAML authentication in an existing domain.
You use the Administrator tool to configure a web application to use a different identify provider. To configure the Administrator tool or the monitoring application to use a different identity provider, you modify the SAML configuration on the node where the application runs. To configure other web applications to use a different identity provider, you modify the SAML configuration within the application process.


Updated June 26, 2020