IDaaS Open Platform

Mincai HR System as Identity Source

Identity Source

# Overview

IDaaS supports enterprises in importing user and organizational information to the IDaaS platform through various identity source channels. This article explains how to configure the Mincai HR system as an identity source within the IDaaS platform to achieve synchronization of organizational and user data.

# Prerequisites

  • Possess administrator permissions for the Mincai HR System Open Platform.
  • Possess administrator permissions for the IDaaS Enterprise Center platform.

# Configuration Process

# Steps

# Create an Application on the Mincai HR Open Platform

  1. Create a custom enterprise application on the Mincai HR Open Platform. For detailed steps, please refer to the platform's relevant documentation.
  2. Obtain parameters such as the appKey and appSecret for the custom application.
  3. Grant users access permissions to the newly created application.

# Configure Mincai HR as an Identity Source in IDaaS

  1. Log in to the IDaaS Enterprise Center platform. In the top navigation bar, select "Users > Identity Source Management", click "Add Identity Source", and choose the "Mincai HR" identity source.

  1. Set a custom name for the identity source. Fill in the parameters such as appKey, appSecret, and Base URL as prompted on the interface. Click "OK" to save after configuration.

  2. Navigate to the details page of the newly added identity source. You can view and update the "Basic Configuration" of the Mincai HR identity source, including connection parameters and synchronization mechanisms.

  1. Switch to the "Advanced Configuration" tab. It is recommended to keep the default settings or fill them in based on actual requirements.

Parameter Description
Select Root Organization Select an organizational node in IDaaS to serve as the root node for the synchronized Mincai HR organizations.
Organization Matching Strategy By default, the organization code in IDaaS is associated with the institution code in Mincai HR.
Create Organization Default is Yes.
Update Organization Default is Yes.
Delete Organization Default is "Retain Organization" (i.e., organization deleted in Mincai HR is retained in IDaaS). Also supports disabling or deleting the organization.
User Matching Strategy By default, the user's mobile number and username in IDaaS are associated with the user's mobile number and username in Mincai HR.
Create User Default is Yes.
Update User Default is Yes.
Delete User Default is "Disable User" (i.e., user deleted in Mincai HR is disabled in IDaaS). Also supports retaining or deleting the user.
Security Threshold Adjustment Set the maximum threshold percentage for changes such as user deletion, organization deletion, or organizational hierarchy changes when they occur in the upstream identity source.
Threshold = (Difference between data already recycled by the platform and data to be recycled this time / Data already recycled) * 100%. When the upstream identity source application disables/deletes data exceeding the set threshold, the platform will not perform the disable/delete operations upon receiving the instruction.
  1. After configuration, switch to the "Object Model" tab and select "Mapping Definition". Configure the mapping relationships between the attributes of organizations and users in the Mincai HR system and the attributes of organizations and users in IDaaS according to your project's actual needs.

The Object Model supports mapping attributes from users and organizations in the Mincai HR identity source to corresponding attributes of users and organizations in IDaaS. Once configured, this enables the recycling of user and organization attributes from Mincai HR to IDaaS.

  • Execution Method: Sets under which circumstances the attribute needs to be mapped.
    • No Mapping: This attribute will not be synchronized to IDaaS.
    • Create: This attribute will only be synchronized during creation.
    • Update: This attribute will only be synchronized during updates.
    • Create and Update: This attribute will be synchronized during both creation and updates.
  • Conversion Method: Sets the method for attribute mapping.
    • Automatic Conversion: Synchronizes the value as-is from the identity source.
    • Script Conversion: Use this method to transform the value from the identity source if it does not meet the required format. Please refer to Script Mapping Method.

  1. After the object model configuration is completed, click "Execute Synchronization" to immediately perform the synchronization operation.

    If the synchronization mechanism in the basic configuration is set to scheduled synchronization, there is no need to manually execute the synchronization task here.

  2. After execution is complete, switch to the "Synchronization Events" page to view all synchronization tasks for this identity source. Click "Details" under the "Actions" column to view the import results, or go to the "Users > Users & Organizations" page to view the imported data.

2haohr as Identity Source