Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Organisation Search

Objective

The Mukta Organisation Search service is designed to provide secure and efficient access to organisation data. It incorporates configurable masking patterns and role-based policies to safeguard sensitive information while maintaining accessibility for authorized users.

PII data - Door No, Street Name, Locality, Mobile Number, Email ID, PAN, GSTIN.

The response would be based on the config set in MDMS-V2 which masks the above fields in appropriate patterns.

Features

  1. Role-Based Attribute Access:

    1. Ensures that only authorized roles can access sensitive organisation attributes in plain text.

    2. Configurable access levels for each role.

  2. Configurable Masking Patterns:

    1. Provides flexibility to define masking patterns for each attribute.

    2. Masks sensitive information to ensure data security.

  3. Dynamic Masking Configurations:

    1. Uses MDMS (Master Data Management System) for dynamic retrieval of masking configurations.

Input Request Example

Output Response Example

  • For a user without plain text access:

  • For a user with plain text access:

Key Components

  1. MDMS Configuration Fetching:

    1. Retrieves masking patterns and role-based policies dynamically from MDMS.

  2. Role-Based Masking Logic:

    1. Determines access levels for each role.

    2. Applies appropriate masking patterns to sensitive attributes.

  3. Dynamic Masking of Attributes:

    1. Masks attributes such as name, registration number, and address based on user roles and configurations.

    2. Handles complex paths within objects (e.g., geoLocation.boundaryCode).

Example Workflow

  1. User Request:

    1. The user sends a search request with RequestInfo and SearchCriteria.

  2. Configuration Fetching:

    1. Service fetches masking patterns and role-based policies from MDMS.

  3. Attribute Masking:

    1. Attributes are masked/unmasked based on user roles and configurations.

  4. Response Generation:

    1. Returns the masked/unmasked organisation data to the user.

Curl:

PreviousIndividual Search
NextBill Scheduler

Last updated

Was this helpful?