Table of Contents

Search

  1. Preface
  2. Analyst Service
  3. Catalog Service
  4. Content Management Service
  5. Data Integration Service
  6. Data Integration Service Architecture
  7. Data Integration Service Management
  8. Data Integration Service Grid
  9. Data Integration Service REST API
  10. Data Integration Service Applications
  11. Data Privacy Management Service
  12. Enterprise Data Preparation Service
  13. Interactive Data Preparation Service
  14. Informatica Cluster Service
  15. Mass Ingestion Service
  16. Metadata Access Service
  17. Metadata Manager Service
  18. Model Repository Service
  19. PowerCenter Integration Service
  20. PowerCenter Integration Service Architecture
  21. High Availability for the PowerCenter Integration Service
  22. PowerCenter Repository Service
  23. PowerCenter Repository Management
  24. PowerExchange Listener Service
  25. PowerExchange Logger Service
  26. SAP BW Service
  27. Search Service
  28. System Services
  29. Test Data Manager Service
  30. Test Data Warehouse Service
  31. Web Services Hub
  32. Application Service Upgrade
  33. Appendix A: Application Service Databases
  34. Appendix B: Connecting to Databases from Windows
  35. Appendix C: Connecting to Databases from UNIX or Linux
  36. Appendix D: Updating the DynamicSections Parameter of a DB2 Database

SAML Configuration

SAML Configuration

The Mass Ingestion Service can use a SAML identity provider after you set the SAML configuration options.
The following table describes the properties you can set in
SAML Configuration
section:
Property
Description
Web Application ID
Optional. The ID of web application.
Identity Provider URL
Optional. The URL for the identity provider server. You must specify the complete URL string.
Service Provider ID
Optional. The relying party trust name or the service provider identifier for the domain as defined in the identity provider.
Assertion Signing Certificate Alias
Optional. The alias name specified when importing the identity provider assertion signing certificate into the truststore file used for SAML authentication.
If you change the alias name, import the corresponding certificate into the truststore file on each gateway node, and then restart the node.
Clock Skew Tolerance
Optional. The allowed time difference between the identity provider host system clock and the system clock on the master gateway node.
The lifetime of SAML tokens issued by the identity provider by is set according to the identity provider host system clock. The lifetime is valid if the start time or end time set in the token is within the specified number seconds of the system clock on the master gateway node.
Values must be from 0 through 600 seconds. Default is 120 seconds.