This Repository contains configurations for Inji Stack, These are the split up of the properties used by different modules in the inji stack
- inji-default.properties - Default Configuration for Inji Mobile App is mentioned here
- credential-template.html - PDF Template for Inji Web Credential Download is mentioned here
- mimoto-default.properties - Default Configuration for Mimoto App is mentioned here
- mimoto-issuers-config.json - Configuration of All Supported Credential Issuers is mentioned here
- mimoto-trusted-verifiers.json - Configuration of All Trusted Credential Verifiers is mentioned here
- The response_uri is used to receive vp_token for cross device flow support.
- A mock configuration for the
mock-verifieris provided to represent a verifier that supports only signed requests. Currently, Inji Verify does not support signed requests, but the wallet supports both signed and unsigned requests. Therefore, this configuration is only for demonstration purposes.
- data-share-default.properties - Default Configuration for Datashare is mentioned here
- data-share-standalone.properties - Standalone Configuration for Datashare is mentioned here, which lets you use datashare service without PMS
certify-default.properties - This file holds only the certify's core properties and will have the last section for properties that is suppose to be overridden by the plugin-usecase properties
Right now we will be maintaining the below 3 plugin-usecase property files, one for each plugin that is readily available for certify integration. And each plugin is associated with an example usecase.
- certify-mock-identity.properties - Uses mock plugin and showcases identity usecase
- certify-mosipid-identity.properties - Uses mosip identity plugin and showcases identity usecase
- certify-sunbird-insurance.properties - Uses sunbird RC plugin and showcases insurance usecase
- certify-postgres-landregistry.properties - Uses posgtres dataprovider plugin and showcases land registry and land statement usecases
Each plugin-usecase property file will contain the below 3 sections
- Properties to enable the plugin
- Properties specific to plugins
- Properties that is available in the certify-default.properties but needs to be overriden specific to the usecase