README.md

Overview

This is the docker-compose setup to run mimoto which act as BFF for Inji mobile and backend for Inji web. This is not for production use.

What is in the docker-compose folder?

1. certs folder holds the p12 file which is being created as part of OIDC client onboarding.
2. "config" folder holds the mimoto system properties file, issuer configuration and credential template.
3. "docker-compose.yml" file with mimoto setup.

How to run this setup?

1. Add Id providers as an issuer in mimoto-issuers-config.json

2. Add verifiers clientId and redirect Uris in mimoto-trusted-verifiers.json for Online Sharing

3. Start esignet services and update esignet host references in mimoto-default.properties and mimoto-issuers-config.json

4. Start the data share services and update data share host references in mimoto-default.properties. data share service helm is available in the Inji Web Helm

5. Create certs folder in the same directory and create OIDC client. Add key in oidckeystore.p12 and copy this file under certs folder. Refer here to create client

• Update client_id and client_alias as per onboarding in mimoto-issuers-config.json file.

5. Start the docker-compose file

docker-compose up

7. Access Apis as
   • http://localhost:8099/v1/mimoto/allProperties
   • http://localhost:8099/v1/mimoto/issuers
   • http://localhost:8099/v1/mimoto/issuers/StayProtected
   • http://localhost:8099/v1/mimoto/issuers/StayProtected/well-known-proxy

Note:

• Replace mosipbox.public.url, mosip.api.public.url with your public accessible domain. For dev or local env ngrok is recommended.