Table of Contents

Search

  1. Preface
  2. Introduction
  3. IDD Concepts
  4. Implementation Process
  5. IDD Configuration Manager
  6. Manual IDD Configuration
  7. IDD Global Properties
  8. Sizing and Platform Requirements
  9. Application Components
  10. IDD Security Configuration
  11. Data Security
  12. Example Role-Based Security Configuration
  13. Data Masking
  14. Siperian BPM Workflow Engine
  15. Locale Codes
  16. Troubleshooting
  17. Glossary

Data Director Implementation Guide

Data Director Implementation Guide

Custom Login Provider Package

Custom Login Provider Package

The custom login provider package is an archive file that contains Java classes. You can use the Informatica Data Director Configuration Manager to upload the archive file. The custom login provider package must be in a ZIP file.
In the Entity 360 framework, the Custom Login Provider package must be in a ZIP file that contains the following:
  • META-INF folder. This folder contains a MANIFEST.MF file which has a Login-Provider-Class-Name entry that contains a name of a class that implements the LoginProvider interface.
  • JAR file with Custom Login Provider implementation.
  • Other JAR files that contain dependencies for the Custom Login Provider implementation, including utility classes, logging, and third-party libraries.
You can configure the custom login provider package to use the Informatica Data Director login form or the login form of an external identity provider, such as Google or Salesforce.
The following image shows the Informatica Data Director login form:
The Informatica Data Director login form in the Entity 360 framework.
If you do not upload a custom login provider package, the default Informatica Data Director implementation authenticates users against the credentials stored in the MDM Hub master database.

Custom Login Provider Packages in the Resource Kit

The Resource Kit contains sample login provider packages that you can use with the Informatica Data Director application. These single sign-on login packages are stored as both JAR and ZIP files. Database administrators and other technical members of an MDM implementation team can use these files to create their own custom login provider packages.
The sample single sign-on package files are in the following directory:
<
infamdm installation directory
>/hub/resourcekit/samples/sso

0 COMMENTS

We’d like to hear from you!