Table of Contents


  1. Preface
  2. Introduction to MDM Hub Security
  3. Resources
  4. Roles
  5. Users and User Groups
  6. Security Providers
  7. Application Level Security
  8. Password Hashing
  9. Glossary

Certificate-Based Authentication

Certificate-Based Authentication

The MDM Hub uses certificate-based authentication in conjunction with password hashing. Certificates offer another layer of security for users who do not want to input their password when they access trusted applications. By default, the certificate login module considers Informatica applications, such as IDD, to be trusted applications.
To use external applications with certificate-based authentication, the external application passes the MDM Hub a concatenation of the application name and username. For example,
. The external application must also pass a security payload. To generate a security payload, use the security payload generator utility in the Resource Kit. The application user also needs a private key, which must be maintained by the client. For more information about the security payload generator utility, see the
Multidomain MDM Resource Kit Guide
The MDM Hub creates public certificates that you can use for certificate-based authentication, but you can choose to implement a custom certificate provider. To implement a custom certificate provider, you must implement the
interface in the
file, which is in the following directory:
MDM Hub installation directory


We’d like to hear from you!