Overview

Packet Manager performs the following functions:

1. Reads/writes registration packets from/to Object Store.

2. Performs in-memory encryption and decryption of packets.

3. Performs security checks, checksum, file validations, ID object validations etc. on the registration packet.

4. Provides packet information to other services via APIs. In case of multiple packets associated with an ID, pulls information from packets based on configured priority. (See packetmanager.default.priority).

Packet Manager runs as a service and is also available as a library.

The relationship of Packet Manager with other services is explained here. NOTE: The numbers do not signify sequence of operations or control flow. Arrows indicate data flow.

1. Resident Services uses Packet Manager library to create packet.

2. Registration Processor reads packet data using Packet Manager service.

3. Packets are stored and retrieved from Object Store.

4. Audit logs.

5. Encryption and decryption of packet.

6. Registration Client uses Packet Manager library to create packets.

Packet stucture

Refer Registration Packet Structure.

API

Refer API Documentation.

Source code

Github repo.

Overview

A registration packet is a zipped, encrypted file containing ID information of an individual. It contains meta information about operator/supervisor, registration center, machine, devices etc.

Zipped packet

Example zipped file:

10001100771006920220128223618-10001_10077-20220128223618.zip

Naming convention: appid-refid_timestamp.zip

• appid

• refid: centerid_machineid

Unzipped packet

.
└── REGISTRATION_CLIENT
    └── NEW
        ├── 10001100771006920220128223618_evidence.json
        ├── 10001100771006920220128223618_evidence.zip
        ├── 10001100771006920220128223618_id.json
        ├── 10001100771006920220128223618_id.zip
        ├── 10001100771006920220128223618_optional.json
        └── 10001100771006920220128223618_optional.zip

• *_id.zip: Applicant demographic/biometric/document fields which are marked as "pvt" or "kyc" or "none" in ID Schema.

• *_id.json: Meta information (process, encrypted hash, signature, schema version etc.) for *_id.zip file.

• *_evidence.zip: Applicant's demographic/biometric/document fields which are marked as "evidence" or "none" in ID Schema.

• *_evidence.json: Meta information (process, encrypted hash, signature, schema version etc.) for *_evidence.zip file.

• *_optional.zip: Applicant demographic/biometric/document fields which are marked as "optional" or "none" ID Schema.

• *_optional.json: Meta information (process, encrypted hash, signature, schema version etc.) for *_optional.zip file.

Unzipped components

Note: this is a sample packet and doesnot mean a particular information will be always available in same packet. The fields are populated based on the fieldCategory set in schema json.

• Id

id
├── ID.json
├── individualBiometrics_bio_CBEFF.xml
├── packet_data_hash.txt
├── packet_meta_info.json
├── packet_operations_hash.txt
├── proofOfAddress.pdf
├── proofOfIdentity.pdf
└── proofOfRelationship.pdf

• Evidence

evidence
├── ID.json
├── packet_data_hash.txt
├── packet_meta_info.json
├── packet_operations_hash.txt
└── proofOfException.pdf

• Optional

optional
├── ID.json
├── packet_data_hash.txt
├── packet_meta_info.json
└── packet_operations_hash.txt

Sample packet

See sample packet.