Business Entity Services Guide

10.5 HotFix 2
- 10.5
- 10.4 HotFix 3
- 10.4 HotFix 2
- 10.4 HotFix 1
- 10.4
- 10.3 HotFix 3
- 10.3 HotFix 2
- 10.3 HotFix 1
- 10.3

Back Next

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:

Use the credentials of an authenticated user to get an authentication cookie.

Save the authentication cookie.

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.

REST Business Entity Service Calls

Get the Authentication Cookie and Informatica CSRF Token

Create a Person Record

Set the Session Timeout

Get User Information in the Session Login Request

Refresh a Session

Validate a Session

Log Out of a Session