Business Entity Services Guide

10.3 HotFix 1
- 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

Back Next

Authentication Cookies for Login from Third-Party Applications

Use authentication cookies to authenticate the MDM Hub users and call the business entity services from third-party applications. You can obtain a cookie based on the credentials of an authenticated user. Save the cookie and use it to call the SOAP APIs. You need not hard-code the user name and password.

Make the following POST request to log in to the Entity 360 View with your user name and password:

POST http://<host>:<port>/e360/com.informatica.tools.mdm.web.auth/login
{
    user: 'admin',
    password: 'user password'
}

When the login operation is successful, the server returns the authentication cookie in the

set-cookie

header field. The following sample code shows a

set-cookie

in the response header:

Set-Cookie: auth_hash_cookie="admin===QTc1RkNGQkNCMzc1RjIyOQ==";
Version=1; Path=/

Store the hash and use it in the request header of your API calls. You need not provide a user name and a password for the API calls.

The following example shows how to use an authentication cookie in your API request header:

GET http://<IP of host>/cmx/cs/localhost-orcl-DS_UI1
Cookie: auth_hash_cookie="admin===QTc1RkNGQkNCMzc1RjIyOQ=="

Rename Saved Search

Table of Contents

Business Entity Services Guide

Business Entity Services Guide

Authentication Cookies for Login from Third-Party Applications

Authentication Cookies for Login from Third-Party Applications