Configuration Guide

Overview

The following guide outlines some important properties that can be customized for a given installation. Please note that this list is not exhaustive but serves as a checklist for reviewing properties that are likely to differ from the default settings. For a complete list of properties, refer to the files listed below.

Configuration files

Resident Service uses the following configuration files:

application-default.properties
resident-default.properties
resident-ui-share-credential-schema.json
resident-ui-update-demographics-schema.json
resident-ui-personalized-card-schema.json

Resident Services dependent modules configuration files

Changes are done only in the below config files for dependent modules.

id-repository-default.properties

id-authentication-default.properties

mosip-vid-policy.json

registration-default.properties

Changes done in the MOSIP config repo

Please go to the Files changes section and refer to removed and added properties.

Database

Properties used for configuring the database.

Token generation

URL pattern for logging filter. For example, "/callback/*" .Defaults to "/*".

Rest template logger filter

This will print the request details such as URL, headers, and body for debugging purposes. The default is false.

DB calls logger filter

This will print the repository method calls for debugging purposes. The default is false.

Micrometer metrics for DB response time & rest template API call response time

Websub topic subscription and WebsubCallbackRequestDecoratorFilter

Partner details

DB properties to skip automatic table creation in startup

Allowed Authentication types and default unlock duration

These are the authentication types allowed for a resident and default unlock duration.

Template type codes for allowed Auth-type list (auth.types.allowed)-

Templates type codes for authentication types

Template type codes for Auth-type status-

Templates type codes for authentication types status

Validation properties

Below are the properties used for validation purpose.

Security

Keycloak authentication client

Keycloak authentication allowed audience

Mapping Identity json to map with the applicant id json

Machine creation and search configs

Properties used for machine specification and center

Auth Adapter rest template authentication configs

Exclusion list of URL patterns that should not be part of authentication and authorization

Property used to define the endpoints that should not be part of authentication.

Configuration for google re-captcha

Comma separated values of property keys to be exposed to UI

This property is used to define the keys of the properties to be exposed to UI.

Auth allowed urls

MOSIP eSignet config

When enabling MOSIP eSignet comment Mock Keycloak config, vise versa.

Auth Adapter ValidateTokenHelper

This property will directly apply the certs URL without the need for constructing the path from the issuer URL. This is useful to keep a different certs URL for integrating with MOSIP IDP for offline token validation.

Resident login configuration for eSignet

User-info claim attributes

Used in open-id-connect based login with UIN/VID in MOSIP-IDP

Scopes

Used for login purposes

Key manager encryption/decryption configuration

Properties used to define application and reference id.

Object Store configuration

To configure the 'Object Store Configuration', update the 'Object Store URL' and other properties as below:

object.store.s3.url=

Virus Scanner configuration

Property used whether to enable virus scanner flag

VID Policy URL

Property used to get the vid policy json

Resident UI Schema JSON file

Property used to get the UI schema json

Identity Mapping JSON file

Property used to get the identity mapping json

Credential Data format MVEL file name

This property is used to get the data format from MVEL file

WebSub Topic and callback properties for auth-type status event

Below websub properties used for authentication type status event

WebSub Topic and callback properties for auth-transaction status event

Below websub properties used for authentication transaction status event

WebSub Topic and callback properties for credential status event

Below websub properties used for credential status event

WebSub Topic and callback properties for regproc complete workflow event

Below websub properties used for regproc complete workflow event

TokenId generator

Mask functions

Properties used to get the data format from MVEL file.

Batch job configuration for credential status update

Template type codes for email subject

Template type codes for email content

Template type codes for SMS content

Template type codes for purpose (success) content

Template type codes for purpose (in-progress/failure) content

Template type codes for purpose (Cancelled) content

Template type codes for purpose(Identity updated) content

Template type codes for summary (success) content

Template type code for summary (cancelled) content

Template type code for summary (regproc-success) content

Template type codes for acknowledgement PDFs

Template type codes for supporting documents, service history, registration centers and vid card

Template required properties

View history filters

Maximum data to download in a PDF

The Registration centers will be searched based on the distance value in meters from the Geo location identified

Page size in Bell Icon Notification list and view history

Rectangle coordinates for PDF signed data

File name for the downloaded PDFs

Credential request config for sharing credential to partner

Claim names

Value based properties

OTP Flooding

Configure Time limit for OTP Flooding scenario (in minutes).

Maximum file size and types for uploading document

Reg-proc packet status codes

Reg-proc packet transaction type codes

Sequence order of reg-proc transaction type codes

Synchronous events

Asyc Request Types

Asynchronous events

Attributes name based template type codes

Define property name in below format- resident.<attribute name>.template.property.attribute.list

Template type codes for event status code

Template type codes for event types

Define property name in below format- resident.event.type.<eventType>.template.property

Template type codes for service types

Define property name in below format- resident.service-type.<serviceType>.template.property

Template type codes for id-authentication request types description

Define property name in below format- resident.id-auth.request-type.<authTypeCode>.<statusCode>.descr

Template type codes for authentication modes (authTypeCode)

Define property name in below format- resident.auth-type-code.<authTypeCode>.code

Flag to retrieve UIN or VID

Below property will retrieve VID when requested. Default is false so, UIN will be retrieved. Endpoints using below property- /individualId/otp, /aid/status.

Class name of the referenceValidator

Commenting or removing this property will disable reference validator.

Request time validation

For validating request time as per before & after time limit (in seconds) in contact-details/update API.

Date time formatting styles

The java.time.format.FormatStyle enum to use for date time formatting based on locale. Allowed values with examples are:

  • FULL ('Tuesday, April 12, 1952 AD' or '3:30:42pm PST')

  • LONG('January 12, 1952')

  • MEDIUM ('Jan 12, 1952')

  • SHORT ('12.13.52' or '3:30pm')

Current value is MEDUIM. For more details refer to the enum.

Cache expiration time (in milliseconds)

Separators

Usage: resident.attribute.separator.<attribute>=<separator string>

Thread properties

Async thread for audit calls. Limit the number of async threads created in Resident services. This count is divided into 4 thread groups configured in 'io.mosip.resident.config.Config' class.

Logo property

This property is used in all downloaded PDF files.

Map (zoom in & out)

These properties are used in reg-center feature for map zoom in & out.

Transliteration workaround properties

Transliteration work around property since eng to fra directly is not supported in icu4j.This can be added for any other unsupported language also.

For example, resident-transliteration-workaround-for-<fromLanguageCode>-<toLanguageCode> = fromLanguageCode-intermediateLanguageCode-toLanguageCode.

For this, intermediate language code transliteration should work in both ways.

Reg-processer-credential-partner-policy-url

This is a policy url to fetch delimeter to download card after updating uin.

The request IDs used in Resident REST APIs

The request versions used in Resident REST APIs

Auth Services API calls

Credential Req & service calls

IdRepo identity Service calls

IdRepo vid Service calls

Key manager API calls

Master Data api calls

Notification service

Partner manager service URLs

Reg-proc service calls

Resident API calls

Other service calls

Identity Mapping json

Below config is used to get identity mapping and get remaining update count for the Identity Attributes .

This is used in Resident in Update UIN feature to show remaining update count for the Identity Attribute.

Mvel File config

This file contains Mvel method definitions for masking attributes, getting passwords, and formatting attributes.

This is used in Resident for downloading PDF cards and for masking attributes in the share credential feature and personalize card feature.

Last updated

Was this helpful?