Registration with Client User ID (Server Side)

Registration of an account when eSuite is the secondary IDM and the link into the eSuite platform is via the Primary IDM's identifier which is stored in the Client User Id within eSuite. This registration need to be processed through a middle ware server as no End User authentication is passed through to eSuite as it is expected in future as authentication has been performed by the primary IDM platform prior to calling to eSuite.

Description

The diagram below shows the Server-Side implementation of user registration flow. In this flow the browser calls into [Client Company]’s [Primary IDM]. Once the user is created in [Primary IDM] the middleware will then call the eSuite platform using a single API call to create an account using the [Primary IDM] identifier as the account’s Client User ID. 

Workflow

 

Authentication

As these are server-side API being called then server-side authentication is used for the API. API authentication method details can be found here: https://supportstaging.mppglobal.com/technical/esuite-rest-api-support/authenticating/

eSuite Authentication Prerequisite

To enable access to Server Side API's eSuite MPP Global will provide the following:
  • Client ID
  • Client API Password
These settings will be provided for both the UAT and Production environment as these will be different between environments.

API Documentation

Details on the API used in this diagram can be found at the links below: