Table of Contents

Search

  1. Preface
  2. Introduction to Business Entity Services
  3. EJB Business Entity Service Calls
  4. REST Business Entity Service Calls
  5. REST APIs for Data Director
  6. SOAP Business Entity Service Calls
  7. Cross-reference Records and BVT Calculations Services
  8. Supporting Corporate Linkage Service
  9. External Calls to Cleanse, Analyze, and Transform Data
  10. Appendix A: Using REST APIs to Add Records
  11. Appendix B: Using REST APIs to Upload Files
  12. Appendix C: Using REST APIs to Manage Reports

Authentication Cookies for Login from Third-Party Applications

Authentication Cookies for Login from Third-Party Applications

Use authentication cookies to authenticate MDM Hub users and call business entity services from third-party applications, such as Postman. With the use of authentication cookies, you don't need to hard-code the user name and password in the HTTP header.
The process for using authentication cookies includes the following steps:
  1. Use the credentials of an authenticated user to get an authentication cookie.
  2. Save the authentication cookie.
  3. Use the authentication cookie to call REST APIs.
All MDM sessions use an Informatica CSRF Token (ICT). An ICT appears in the HTTP header.
When a user requests a session ID, the response returns an ICT in the HTTP header. For external applications, you get a URL for authentication that the external applications can use. This URL returns a
mdmsessionid
authentication cookie and an ICT that is in the header. The authentication cookie is an MDM session ID. For any subsequent business entity services calls, the call must include the authentication cookie and the ICT
When you send a request to get the authentication cookie and ICT, the
userinfo
section is optional.
To manage sessions, use REST calls.

0 COMMENTS

We’d like to hear from you!