Table of Contents

Search

  1. Preface
  2. Introduction to Business Entity Services
  3. Enterprise Java Bean Business Entity Service Calls
  4. Representational State Transfer Business Entity Service Calls
  5. Simple Object Access Protocol Business Entity Service Calls
  6. Services for Cross-reference Records and BVT Calculations
  7. Supporting Corporate Linkage Service
  8. External Calls to Cleanse, Analyze, and Transform Data
  9. Using REST APIs to Add Records
  10. Using REST APIs to Upload Files

Authentication Cookies for Login from Third-Party Applications

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 REST 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>:8080/cmx/cs/localhost-orcl-DS_UI1/Person?action=meta Cookie: auth_hash_cookie="admin===QTc1RkNGQkNCMzc1RjIyOQ=="

0 COMMENTS

We’d like to hear from you!