Resident Portal Configuration Guide
The provided guide presents a list of essential properties that can be customised according to a specific installation. Please note that this list is not exhaustive but rather acts as a checklist to review properties that are expected to differ from their default settings. If you require access to all properties, please refer to the files mentioned below.
Configuration files
Resident Service uses the following configuration files:
application-default.properties
resident-default.properties
resident-ui-personalized-card-schema.json
resident-ui-share-credential-schema.json
resident-ui-update-demographics-schema.json
Database
Properties used for configuring the database.
mosip.resident.database.hostname=postgres-postgresql.postgres
mosip.resident.database.port=5432
javax.persistence.jdbc.driver=org.postgresql.Driver
javax.persistence.jdbc.url=jdbc:postgresql://${mosip.resident.database.hostname}:${mosip.resident.database.port}/mosip_resident
javax.persistence.jdbc.user=residentuser
javax.persistence.jdbc.password=******Token generation
Online Verification Partner
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:
Validation properties
Below are the properties used for validation purpose:
Security
Keycloak authentication client
Keycloak authentication allowed audience
Identity mapping json file
Property used to get the identity mapping json
Machine creation and search configurations
Properties used for machine specification and center:
Auth Adapter rest template authentication configurations
Exclusion list
This is an exclusion list of URL patterns that should not be a part of authentication and authorization.
Properties used to define the endpoints that should not be part of authentication.
Configuration for re-captcha
Resident UI properties
These properties (comma separated values) are used to define the keys of the properties to be exposed to UI.
MOSIP e-Signet configuration
Auth Adapter ValidateTokenHelper
This property will directly apply the certs URL without the need for constructing the path from issuer URL. This is useful for keeping different certs URL for integrating with MOSIP e-Signet for offline token validation.
Resident login configurations for e-Signet
User-info claim attributes
Used in open-id-connect based login with UIN/VID in MOSIP e-Signet(IDP)
Scopes
Used for login purpose:
Key manager encryption/ decryption configuration
Properties used to define application and reference id.
Object Store configuration
For Minio: object.store.s3.url=http://minio.minio:9000
For AWS: object.store.s3.url=s3.${s3.region}.amazonaws.com
Virus Scanner configuration
Property used 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
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 are 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:
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 terms and conditions
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 summary (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
Registration Center search configuration
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
Token related configuration
Rectangle coordinates for PDF signed data
File name for the downloaded PDFs
Credential request configuration
Claim names
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
Synchronous events
Asyc Request Types
Asynchronous events
Attributes name based template type codes
Define property name in below format-
resident..template.property.attribute.list
Class name of the referenceValidator
Commenting or removing this property will disable reference validator.
Cache expiration time (in milliseconds)
Request time validation
For validating request time as per before and 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.
Logger related properties
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 purpose. Default is false.
Websub properties
Last updated
Was this helpful?